Installing the Latest Update From The Launcher Causes Windows to Reboot

[mkel2010]

I used the launcher today to install the latest update. Towards the end of the process, I suddenly received the Windows "Restarting" screen and the computer rebooted. On restart I did a Repair DCS and ran it through the slow option. That reported everything was updated correctly. There are three log files that are timestamped around the time this all occurred. I don't think they show anything but are attached anyway.

dcs.log cef_log.log dcs.log.old

[zildac]

I had the same reboot required message. I'm assuming there was a component (.NET framework perhaps) that was also updated.

[mkel2010]

7 minutes ago, zildac said:

I had the same reboot required message. I'm assuming there was a component (.NET framework perhaps) that was also updated.

If properly coded, the component that needs to reboot should warn the user ahead of time and not arbitrarily reboot a system. If what you described is truly the reason, then there is a bug in the process.

[AtlasR1se]

I haven't played DCS since the last major update due to this issue.

Managed to get it to load in and created a fast mission, tabbed out to another screen and bam, full system restart with no warnings.

Getting cheesed off with ED and the amount of bugs they manage to create to make this unplayable.

When it reboots, there are no crash logs to report the issue either.

Launcher was creating an instant crash, as I said managed to get a fast mission started without launching from the gash launcher.

Edited August 9, 2024 by AtlasR1se

[rob10]

4 minutes ago, AtlasR1se said:

I haven't played DCS since the last major update due to this issue.

Managed to get it to load in and created a fast mission, tabbed out to another screen and bam, full system restart with no warnings.

Getting cheesed off with ED and the amount of bugs they manage to create to make this unplayable.

When it reboots, there are no crash logs to report the issue either.

Launcher was creating an instant crash, as I said managed to get a fast mission started without launching from the gash launcher.

Sorry, but if this was strictly a DCS bug you'd be seeing posts all over about it.  There aren't many.  Typically if it's crashing you to a full system restart you should be checking your hardware to start.

[mkel2010]

55 minutes ago, AtlasR1se said:

I haven't played DCS since the last major update due to this issue.

Managed to get it to load in and created a fast mission, tabbed out to another screen and bam, full system restart with no warnings.

Getting cheesed off with ED and the amount of bugs they manage to create to make this unplayable.

When it reboots, there are no crash logs to report the issue either.

Launcher was creating an instant crash, as I said managed to get a fast mission started without launching from the gash launcher.

 

As @rob10 said, you've likely got more issues with your hardware. Windows is finicky sometimes and not easy to troubleshoot. My issue was just during the update, otherwise DCS is solid on my machine. Google system file checker and run that first to make sure you don't have a corrupt operating system. You can also dig through the Windows Event logs to around the time of a crash to see if you can get an idea what's causing your issues.

[scommander2]

1 hour ago, zildac said:

(.NET framework perhaps)

A special version and not from the regular Windows update? Okay, good to know, thanks.

Edited August 9, 2024 by scommander2

[SOAR]

Same here. Windows 11 Pro, Was updating thru the launcher with about 20 gigs left to download, stepped away to make dinner, came back to the Windows setup screen.

[zildac]

If properly coded, the component that needs to reboot should warn the user ahead of time and not arbitrarily reboot a system. If what you described is truly the reason, then there is a bug in the process.

I was prompted to reboot. It was not automatically initiated by the installer.

[DD_Friar]

53 minutes ago, zildac said:

I was prompted to reboot. It was not automatically initiated by the installer.

That is the experience I had as well. I too assumed a system component (like .NET) was updated as part of the release. 

[silverdevil]

18 hours ago, mkel2010 said:

I used the launcher today to install the latest update. Towards the end of the process, I suddenly received the Windows "Restarting" screen and the computer rebooted. On restart I did a Repair DCS and ran it through the slow option. That reported everything was updated correctly. There are three log files that are timestamped around the time this all occurred. I don't think they show anything but are attached anyway.

look for date of your C:\Program Files\Eagle Dynamics\DCS World OpenBeta\autoupdate_log.txt. look in event viewer application log for around same time. i have this entry.

Log Name:      Application
Source:        MsiInstaller
Date:          8/9/2024 4:41:36 PM
Event ID:      1029
Task Category: None
Level:         Information
Keywords:      Classic
User:          
Computer:      
Description:
Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Restart required. The installation or update for the product required a restart for all changes to take effect.  The restart was deferred to a later time.

 

i have four separate events.

Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810 -- Installation completed successfully.

Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Product Version: 14.40.33810. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

Windows Installer requires a system restart. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Product Version: 14.40.33810. Product Language: 1033. Manufacturer: Microsoft Corporation. Type of System Restart: 2. Reason for Restart: 1.

Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Restart required. The installation or update for the product required a restart for all changes to take effect.  The restart was deferred to a later time.

Ending a Windows Installer transaction: C:\ProgramData\Package Cache\{59CED48F-EBFE-480C-8A38-FC079C2BEC0F}v14.40.33810\packages\vcRuntimeAdditional_amd64\vc_runtimeAdditional_x64.msi. Client Process Id: 14892.

Edited August 10, 2024 by silverdevil

[mkel2010]

1 hour ago, silverdevil said:

look for date of your C:\Program Files\Eagle Dynamics\DCS World OpenBeta\autoupdate_log.txt. look in event viewer application log for around same time. i have this entry.

Log Name:      Application
Source:        MsiInstaller
Date:          8/9/2024 4:41:36 PM
Event ID:      1029
Task Category: None
Level:         Information
Keywords:      Classic
User:          
Computer:      
Description:
Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Restart required. The installation or update for the product required a restart for all changes to take effect.  The restart was deferred to a later time.

 

i have four separate events.

Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810 -- Installation completed successfully.

Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Product Version: 14.40.33810. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

Windows Installer requires a system restart. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Product Version: 14.40.33810. Product Language: 1033. Manufacturer: Microsoft Corporation. Type of System Restart: 2. Reason for Restart: 1.

Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Restart required. The installation or update for the product required a restart for all changes to take effect.  The restart was deferred to a later time.

Ending a Windows Installer transaction: C:\ProgramData\Package Cache\{59CED48F-EBFE-480C-8A38-FC079C2BEC0F}v14.40.33810\packages\vcRuntimeAdditional_amd64\vc_runtimeAdditional_x64.msi. Client Process Id: 14892.

 

I took a look at the Autoupdate Log (in my case marked as the old log because of the repair I did following the reboot.) Interestingly, the log ends with the following lines:

 

00086.362 STATUS: Cleaning up...
00086.362 STATUS: Cleaning up...
00086.501 STATUS: Successfully updated to 2.9.7.58923
00086.501 STATUS: Asking Yes/No: OS restart is required before running the application. Restart now?
00086.501 STATUS: Got YES when asked: OS restart is required before running the application. Restart now?
00086.513 === Log closed

 

I never was prompted to give permission to reboot so clearly this is a bug in the updater or the update process. I was sitting there watching the update so I know for a fact the prompt was never issued. The log file is attached and I am tagging @BIGNEWY.

In reviewing the Windows System Event Log, I found the Event where the reboot was initiated:

The process C:\Program Files\Eagle Dynamics\DCS World\bin\DCS_updater.exe (XXXX) has initiated the restart of computer XXXXX on behalf of user XXXXX\Mark for the following reason: Application: Installation (Planned)
 Reason Code: 0x80040002
 Shutdown Type: restart
 Comment: OS restart is required before running the application.

EDIT:  A Bug report has been submitted.

autoupdate_log_old.txt

Edited August 10, 2024 by mkel2010

[silverdevil]

27 minutes ago, mkel2010 said:

EDIT:  A Bug report has been submitted.

ED is running the installations of the runtime updates for C++ silently. rebooting without prompt has been a known issue with .NET assemblies running silently throughout .NET 3/3.5 existence. i have an MFA component that i have never been able to get a prompt for restart when running silently. it is on hundreds of client computers. this is likely not an issue with ED code and more likely an MS issue. but it is standard practice to at least warn the user that a reboot may happen.

Edited August 10, 2024 by silverdevil

[rob10]

When I finally got done downloading the update I did get the prompt to restart system or cancel.

[mkel2010]

9 minutes ago, silverdevil said:

ED is running the installations of the runtime updates for C++ silently. rebooting without prompt has been a known issue with .NET assemblies running silently throughout .NET 3/3.5 existence. i have an MFA component that i have never been able to get a prompt for restart when running silently. it is on hundreds of client computers. this is likely not an issue with ED code and more likely an MS issue. but it is standard practice to at least warn the user that a reboot may happen.

 

It may well be a Microsoft issue. That said, I run a number of other programs that require .NET frameworks or other run times to be installed as part of an installation or update. NONE of them use a silent installation. This is a choice by someone at ED to run them silently and in my experience it doesn't have to be done that way. My computer is used for many things and there may be (often is) a reason I wouldn't want to reboot arbitrarily since other processes might be running.

[silverdevil]

15 minutes ago, mkel2010 said:

This is a choice by someone at ED to run them silently and in my experience it doesn't have to be done that way.

agreed.

the app i mentioned is provided in the MECM software center, and i chose silent /quiet switch. the app is dependent on .NET so there is no choice with silent to prompt for restart. after all that is what /quiet switch makes the app do. 

[AtlasR1se]

On 8/9/2024 at 11:35 PM, mkel2010 said:

As @rob10 said, you've likely got more issues with your hardware. Windows is finicky sometimes and not easy to troubleshoot. My issue was just during the update, otherwise DCS is solid on my machine. Google system file checker and run that first to make sure you don't have a corrupt operating system. You can also dig through the Windows Event logs to around the time of a crash to see if you can get an idea what's causing your issues.

Never had this issue at all before the update 2.9. xxx. DCS is the only game I get any issues with AT ALL. 

To be honest mate, I really ain't got the patience to sift through event logs just to play a game, I will just leave it until such a time it gets fixed somehow.

[mkel2010]

So I've been having a back and forth email conversation with ED regarding my bug report. The last two messages I received are pasted below. Bottom line: this is the first time a DCS update has required a reboot and the programmers are aware of the issue and are looking for a fix.

"Programmers are already aware of the problem and may be able to find a way to prevent the game from restarting the system without user permission in future updates.
I once again apologize on behalf of the ED management for what happened.

Sincerely yours
Alexander Maximov"

AND

"Mark, this is the first update that requires a system reboot. I sincerely hope that such updates will not become the norm for DCS.
Good luck!

Sincerely yours
Alexander Maximov"