PrimalScript upgrade causes unexpected restart.

Use this forum to ask questions about installation or issues encountered while installing our software.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
User avatar
jvierra
Posts: 13682
Joined: Tue May 22, 2007 9:57 am
Contact:

PrimalScript upgrade causes unexpected restart.

Post by jvierra » Wed Aug 14, 2019 12:32 pm

Product: PowerShell Studio 2019 (64 Bit)
Build: v5.6.166
OS: Windows 10 Pro (64 Bit)
Build: v10.0.17763.0

FYI -
Upgrading to PrimalScript causes an unannounced restart. See event

Code: Select all

Log Name:      System
Source:        User32
Date:          8/14/2019 3:21:37 PM
Event ID:      1074
Task Category: None
Level:         Information
Keywords:      Classic
User:          SYSTEM
Computer:      Alpha
Description:
The process msiexec.exe has initiated the restart of computer ALPHA on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
 Reason Code: 0x80030002
 Shutdown Type: restart
 Comment: The Windows Installer initiated a system restart to complete or continue the configuration of 'PrimalScript 2019'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="User32" Guid="{b0aa8734-56f7-41cc-b2f4-de228e98b946}" EventSourceName="User32" />
    <EventID Qualifiers="32768">1074</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2019-08-14T19:21:37.769472800Z" />
    <EventRecordID>34588</EventRecordID>
    <Correlation />
    <Execution ProcessID="584" ThreadID="4672" />
    <Channel>System</Channel>
    <Computer>Alpha</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="param1">msiexec.exe</Data>
    <Data Name="param2">ALPHA</Data>
    <Data Name="param3">No title for this reason could be found</Data>
    <Data Name="param4">0x80030002</Data>
    <Data Name="param5">restart</Data>
    <Data Name="param6">The Windows Installer initiated a system restart to complete or continue the configuration of 'PrimalScript 2019'.</Data>
    <Data Name="param7">NT AUTHORITY\SYSTEM</Data>
  </EventData>
</Event>
No warning was received.

User avatar
jvierra
Posts: 13682
Joined: Tue May 22, 2007 9:57 am
Contact:

Re: PrimalScript upgrade causes unexpected restart.

Post by jvierra » Wed Aug 14, 2019 12:45 pm

Here is the associated update log if needed:
Attachments
pql19setup_4.5.69_080219_x64.log
(948.66 KiB) Downloaded 7 times

User avatar
Alexander Riedel
Posts: 7001
Joined: Tue May 29, 2007 4:43 pm

Re: PrimalScript upgrade causes unexpected restart.

Post by Alexander Riedel » Wed Aug 14, 2019 12:52 pm

We have not really anything in our files which would trigger a restart. However, the new builds all include the updated Visual Studio 2019 runtime.
If that gets updated and triggers a restart, which I think could be your case, it is beyond our control and we would not get a chance to issue a warning.
That is in a Microsoft created MSI. We'll see what we can find out though.
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
jvierra
Posts: 13682
Joined: Tue May 22, 2007 9:57 am
Contact:

Re: PrimalScript upgrade causes unexpected restart.

Post by jvierra » Wed Aug 14, 2019 1:07 pm

Here is the vc_runtime log which seems to be forcing the restart:
Attachments
dd_vcredist_x86_20190814151855_000_vcRuntimeMinimum_x86.log
(2.61 KiB) Downloaded 4 times

User avatar
jvierra
Posts: 13682
Joined: Tue May 22, 2007 9:57 am
Contact:

Re: PrimalScript upgrade causes unexpected restart.

Post by jvierra » Wed Aug 14, 2019 1:12 pm

Alexander Riedel wrote:
Wed Aug 14, 2019 12:52 pm
We have not really anything in our files which would trigger a restart. However, the new builds all include the updated Visual Studio 2019 runtime.
If that gets updated and triggers a restart, which I think could be your case, it is beyond our control and we would not get a chance to issue a warning.
That is in a Microsoft created MSI. We'll see what we can find out though.
Yes - I know that I just wanted you to be aware that it can happen if anything has the VS or VC files loaded. It is annoying that the system just jumps to light blue screen that says restarting. My edits were lost and I had to start over. For me this can happen because I do development and, at time, things go wrong. Others may be upset so beware. It happens.

I wonder if you can add "NORESTART" to the MSI launch, check the log and tell user to restart.

Again - not critical just information.