Original Message:
Sent: 7/25/2024 5:42:00 AM
From: Ian Wilcox
Subject: RE: Windows 11 in place upgrades
Hello Sidnei, thanks for your response.
For testing I went back to basics to see if there was a particular switch that may have been causing it so I used the simplified command line: setup.exe /auto upgrade /quiet /eula accept /noreboot /copylogs c:\temp However it was still causing the same issue.
Eventually I implemented a workaround of removing the restart task from the upgrade policy and creating a separate power control task which is used after the upgrade policy has completed. I contacted Broadcom support and they think that the upgrade process/thread is not released when the reboot is in same policy causing the unwanted BSOD.
It's not an ideal solution but after performing the upgrade on some more devices it seems to work reliably.
Original Message:
Sent: Jul 24, 2024 02:35 PM
From: Sidnei Santana
Subject: Windows 11 in place upgrades
Hello, it works for me ...
start /wait c:\Temp\BUILD23H2\Setup.exe /auto upgrade /migratedrivers all /compat ignorewarning /dynamicupdate disable /showoobe none /eula accept /quiet /noreboot /copylogs C:\Temp\Logfiles.log
Restart with Altiris task is ok...
Original Message:
Sent: Jun 21, 2024 05:32 AM
From: Ian Wilcox
Subject: Windows 11 in place upgrades
Hello, we are experiencing an issue when using Altiris to perform an in place upgrade from Windows 10 to Windows 11 and am hoping someone may have had a similar experience and can offer some advice.
The upgrade installs successfully, however it seems that when the computer is rebooted automatically after the installation we see the dreaded BSOD but if the computers are rebooted manually after the upgrade they work fine. I have tried the following so far.
-
Removing the /noreboot switch from the command line so it will reboot when the setup process needs it
-
Using the /noreboot switch in the command line and adding a power control task in the policy to reboot if it is required..
-
Using the /noreboot switch in the command line and then adding a restart task into the policy - shutdown -r
-
Using the /noreboot switch in the command line and then adding a restart task into the policy with 15 minute delay - shutdown -r -t 900
The only way which seems reliable is to use the /noreboot switch in the command line, remove all reboot tasks from the policy and then manually reboot the computer after the upgrade has finished. We have more than 10,000 computers to update so we need to automate the reboot somehow.
Any advise will be greatly appreciated!