I have a problem with the migration from Windows 10 to Windows 11 23H2 via the WSUS. The update 23H2 x64 2025-02B (KB5051989) is published in the WSUS. The update is requested and the installation is performed according to schedule. The installation runs smoothly up to about 48%, after that everything is very fast. The update is displayed as installed and a restart is required. As expected, Windows reboots for the second time at 30% during the restart. However, the entire reboot process takes a good three quarters of an hour until the final cleanup. Until then, no error is displayed. After the restart, however, Windows comes up again with Windows 10. Without displaying an error message.<\/p>\n
I let ChatGPT guide me through the analysis process and no error messages or suspicious entries were found in the Event Viewer. No evidence was even found that the system ever tried to install Windows 11.<\/p>\n
Does anyone know what the problem could be here?<\/p>\n
Please note: The system is capable for the upgrade:<\/p>\n
PS C:\\Windows\\system32> \\Windows\\Temp\\microsoft_windows11_readiness_script.ps1\n{\"returnCode\":0,\"returnReason\":\"\",\"logging\":\"Storage: OSDiskSize=474GB. PASS; Memory: System_Memory=32GB. PASS; TPM: TPMVersion=2.0, 0, 1.38. PASS; Processor: {AddressWidth=64; MaxClockSpeed=2496; NumberOfLogicalCores=16; Manufacturer=GenuineIntel; Caption=Intel64 Family 6 Model 141 Stepping 1; }. PASS; SecureBoot: Capable. PASS; \",\"returnResult\":\"CAPABLE\"}\n<\/code><\/pre>","upvoteCount":5,"answerCount":23,"datePublished":"2025-02-26T13:42:33.606Z","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"},"suggestedAnswer":[{"@type":"Answer","text":"I have a problem with the migration from Windows 10 to Windows 11 23H2 via the WSUS. The update 23H2 x64 2025-02B (KB5051989) is published in the WSUS. The update is requested and the installation is performed according to schedule. The installation runs smoothly up to about 48%, after that everything is very fast. The update is displayed as installed and a restart is required. As expected, Windows reboots for the second time at 30% during the restart. However, the entire reboot process takes a good three quarters of an hour until the final cleanup. Until then, no error is displayed. After the restart, however, Windows comes up again with Windows 10. Without displaying an error message.<\/p>\n
I let ChatGPT guide me through the analysis process and no error messages or suspicious entries were found in the Event Viewer. No evidence was even found that the system ever tried to install Windows 11.<\/p>\n
Does anyone know what the problem could be here?<\/p>\n
Please note: The system is capable for the upgrade:<\/p>\n
PS C:\\Windows\\system32> \\Windows\\Temp\\microsoft_windows11_readiness_script.ps1\n{\"returnCode\":0,\"returnReason\":\"\",\"logging\":\"Storage: OSDiskSize=474GB. PASS; Memory: System_Memory=32GB. PASS; TPM: TPMVersion=2.0, 0, 1.38. PASS; Processor: {AddressWidth=64; MaxClockSpeed=2496; NumberOfLogicalCores=16; Manufacturer=GenuineIntel; Caption=Intel64 Family 6 Model 141 Stepping 1; }. PASS; SecureBoot: Capable. PASS; \",\"returnResult\":\"CAPABLE\"}\n<\/code><\/pre>","upvoteCount":5,"datePublished":"2025-02-26T13:42:33.700Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/1","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"}},{"@type":"Answer","text":"I expect the event logs will have something.<\/p>\n
Checked the Windowsupdate.log?<\/p>\n
The CBS.log?<\/p>","upvoteCount":3,"datePublished":"2025-02-26T14:00:43.375Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/2","author":{"@type":"Person","name":"Rod-IT","url":"https://community.spiceworks.com/u/Rod-IT"}},{"@type":"Answer","text":"
Damn, now the colleague has gone home with his laptop. But I was still able to try out part of your tip. Could it be that incompatible printer drivers during the migration (as described) are causing the problem? I would have found a few hints about this in the event log:<\/p>\n
PS C:\\Windows\\SoftwareDistribution> Get-Content \"C:\\Windows\\SoftwareDistribution\\ReportingEvents.log\" | Select-Object -Last 20\n{72145CCE-E705-41C7-9522-725327A74EA5} 2025-02-26 13:19:19:197+0100 1 522 [AGENT_COMMIT_FAILED] \nCommit Failure: Windows failed to commit the following update with error 0xc1900101: Windows 11, version 23H2 x64\n<\/code><\/pre>\n(the list is much longer)<\/p>\n
PS C:\\Windows\\SoftwareDistribution> Get-WinEvent -LogName \"Microsoft-Windows-DeviceSetupManager/Admin\" | Select-Object TimeCreated, Id, Message\ne-iEet-oNae\"irsf-inosDvcStuMnge/Amn\"| eet-bjctTmCratd,Id Mssge\nTimeCreated Id Message\n----------- -- -------\n26.02.2025 13:28:16 101 Der DSM-Dienst wird beendet. Die Betriebszeit des Diensts betrug 46 Sek...\n26.02.2025 13:27:31 112 Das Gerät \"AV44\" ({00000000-0000-0000-ffff-ffffffffffff}) wurde verarbe...\n26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container \"{...\n26.02.2025 13:27:31 112 Das Gerät \"\\\\COMPANY-PS2\\HLK Typenschilddrucker\" ({f9a96989-3790-5512-8853...\n26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container \"{...\n26.02.2025 13:27:31 112 Das Gerät \"\\\\COMPANY-PS2\\AV Kyocera P3055\" ({d59f09e7-7253-5b7b-ab98-5b998...\n26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container \"{...\n26.02.2025 13:27:30 130 Das Metadatenpaket \"e4e3dd17-c038-47cb-a24c-78c36ffe0471\" wurde für den...\n26.02.2025 13:27:30 112 Das Gerät \"\\\\COMPANY-PS2\\IT Farbe\" ({511014bc-cde8-5e97-a282-9290a38df1fc}...\n26.02.2025 13:27:30 130 Das Metadatenpaket \"38f6b193-c2df-4e1e-846d-244da079031e\" wurde für den...\n<\/code><\/pre>\nBut now my test object has gone home. But we already suspect a certain printer, and we have exactly one department that doesn’t have this printer installed, so I’ll continue testing tomorrow.<\/p>\n
Thank you very much, that was a good push in the right direction. Even if I don’t yet have confirmation that this is the problem, a driver or software problem fits the picture. The Windows 11 readiness script, of course, doesn’t look at anything like that, just the hardware details. The setup could actually only come across the problem during the installation and then perform a silent rollback. Sounds plausible…<\/p>","upvoteCount":0,"datePublished":"2025-02-26T14:56:01.841Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/3","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Cyberduck:<\/div>\n
\nno error messages or suspicious entries were found in the Event Viewer.<\/p>\n<\/blockquote>\n<\/aside>\n
If you’re using PowerShell like in your reply, I wouldn’t as you seem to be looking for specific, and in the wrong place.<\/p>\n
Open Event Viewer and look under application and system for red or yellow warnings around the time of the last reboot. It’s easier to see issues in colour than it is trying to weed out the one you want in PowerShell, especially since you don’t know what you want at this point.<\/p>\n
I’m not sure why you’re in software distribution either, that wasn’t something I suggested.<\/p>\n
If you want to use PowerShell, you should run get-windowsupdatelog<\/code> then view that.<\/p>","upvoteCount":1,"datePublished":"2025-02-26T15:46:25.899Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/4","author":{"@type":"Person","name":"Rod-IT","url":"https://community.spiceworks.com/u/Rod-IT"}},{"@type":"Answer","text":"That’s my first rule of upgrading an OS, always see what’s installed and if it looks old, verify it is compatible before going through the lengthy process. Second rule is to temporarily disable antivirus for the process. Third rule is to cross my fingers.<\/p>","upvoteCount":2,"datePublished":"2025-02-26T16:24:06.433Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/5","author":{"@type":"Person","name":"spiceuser-ti0ay","url":"https://community.spiceworks.com/u/spiceuser-ti0ay"}},{"@type":"Answer","text":"
e4e3dd17-c038-47cb-a24c-78c36ffe0471` is a cab file, and 0x80070490 says “That’s not what I wanted”<\/p>\n
Are you sure you have the right install files?<\/p>","upvoteCount":0,"datePublished":"2025-02-26T23:05:34.573Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/6","author":{"@type":"Person","name":"somedude2","url":"https://community.spiceworks.com/u/somedude2"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Cyberduck:<\/div>\n
\nDamn, now the colleague has gone home with his laptop. But I was still able to try out part of your tip. Could it be that incompatible printer drivers during the migration (as described) are causing the problem? I would have found a few hints about this in the event log:<\/p>\n
PS C:\\Windows\\SoftwareDistribution> Get-Content \"C:\\Windows\\SoftwareDistribution\\ReportingEvents.log\" | Select-Object -Last 20\n{72145CCE-E705-41C7-9522-725327A74EA5} 2025-02-26 13:19:19:197+0100 1 522 [AGENT_COMMIT_FAILED] \nCommit Failure: Windows failed to commit the following update with error 0xc1900101: Windows 11, version 23H2 x64\n<\/code><\/pre>\n(the list is much longer)<\/p>\n
PS C:\\Windows\\SoftwareDistribution> Get-WinEvent -LogName \"Microsoft-Windows-DeviceSetupManager/Admin\" | Select-Object TimeCreated, Id, Message\ne-iEet-oNae\"irsf-inosDvcStuMnge/Amn\"| eet-bjctTmCratd,Id Mssge\nTimeCreated Id Message\n----------- -- -------\n26.02.2025 13:28:16 101 Der DSM-Dienst wird beendet. Die Betriebszeit des Diensts betrug 46 Sek...\n26.02.2025 13:27:31 112 Das Gerät \"AV44\" ({00000000-0000-0000-ffff-ffffffffffff}) wurde verarbe...\n26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container \"{...\n26.02.2025 13:27:31 112 Das Gerät \"\\\\COMPANY-PS2\\HLK Typenschilddrucker\" ({f9a96989-3790-5512-8853...\n26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container \"{...\n26.02.2025 13:27:31 112 Das Gerät \"\\\\COMPANY-PS2\\AV Kyocera P3055\" ({d59f09e7-7253-5b7b-ab98-5b998...\n26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container \"{...\n26.02.2025 13:27:30 130 Das Metadatenpaket \"e4e3dd17-c038-47cb-a24c-78c36ffe0471\" wurde für den...\n26.02.2025 13:27:30 112 Das Gerät \"\\\\COMPANY-PS2\\IT Farbe\" ({511014bc-cde8-5e97-a282-9290a38df1fc}...\n26.02.2025 13:27:30 130 Das Metadatenpaket \"38f6b193-c2df-4e1e-846d-244da079031e\" wurde für den...\n<\/code><\/pre>\nBut now my test object has gone home. But we already suspect a certain printer, and we have exactly one department that doesn’t have this printer installed, so I’ll continue testing tomorrow.<\/p>\n
Thank you very much, that was a good push in the right direction. Even if I don’t yet have confirmation that this is the problem, a driver or software problem fits the picture. The Windows 11 readiness script, of course, doesn’t look at anything like that, just the hardware details. The setup could actually only come across the problem during the installation and then perform a silent rollback. Sounds plausible…<\/p>\n<\/blockquote>\n<\/aside>\n
Would you happen to have access to the Event Viewer (logs) ?<\/p>\n
Then did you do the following<\/p>\n
\ninstall latest firmware for all the hardware ?<\/li>\n run Windows update<\/li>\n remove installed AV and/or security software<\/li>\n<\/ul>","upvoteCount":1,"datePublished":"2025-02-27T06:09:04.839Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/7","author":{"@type":"Person","name":"adrian_ych","url":"https://community.spiceworks.com/u/adrian_ych"}},{"@type":"Answer","text":"\n\n
<\/div>\n
adrian_ych:<\/div>\n
\nWould you happen to have access to the Event Viewer (logs) ?<\/p>\n<\/blockquote>\n<\/aside>\n
Yes, today I had another opportunity to analyze the system more closely, but apart from the two messages that the update was aborted due to the two error codes 0xC1900101 and 0x80242016, I did not find any other suspicious entries. At least not those that were not there before.<\/p>\n
But I did discover something else that I would not have expected. During the whole upgrade process, another Windows 10 update was installed, which was probably not yet completed. Perhaps this is causing problems with the upgrade process.<\/p>\n
---snip---\n[...] 2025-02-26 13:13:17:681+0100 1 521 [AGENT_COMMIT_STARTED] 101 [...] Success Content Commit Commit Started: Windows has started committing the following update: Windows 11, version 23H2 x64 2025-02B \n[...] 2025-02-26 13:19:19:197+0100 1 522 [AGENT_COMMIT_FAILED] 101 [...] Failure Content Commit Commit Failure: Windows failed to commit the following update with error 0xc1900101: Windows 11, version 23H2 x64 2025-02B.\n[...] 2025-02-26 13:23:26:167+0100 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 [...] Success Content Install Installation Successful: Windows successfully installed the following update: 2025-02 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5051974)\n[...] 2025-02-26 13:23:26:198+0100 1 182 [AGENT_INSTALLING_FAILED] 101 [...] Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80242016: Windows 11, version 23H2 x64 2025-02B.\n---snap---\n<\/code><\/pre>\nBeyond that, I can probably rule out my printer drivers as the cause. I have already successfully upgraded a device via WSUS first to Windows 11 23H2 and then to 24H2, and have reset it to Windows 10 with our default software. All GPOs are applied to the device as with the failed machine, and the user is also in the same groups as the user of the failed device, at least with regard to the printer installation. And this test ran without any problems as before.<\/p>\n
So I can rule out a number of group policies and drivers. Of course, the test device is not exactly the same as the user’s device in terms of installed software etc. But my main concern in this test was the printer drivers, which I suspected the most.<\/p>\n
So far, the Windows 10 update remains on the list of suspects.<\/p>","upvoteCount":0,"datePublished":"2025-02-27T17:57:10.230Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/8","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"}},{"@type":"Answer","text":"
Is there AV installed ?\n\n
<\/div>\n
adrian_ych:<\/div>\n
\nIs there AV installed ?<\/p>\n<\/blockquote>\n<\/aside>\n
Yes, Microsoft Defender Business. We usually leave it on because it actually recognizes the upgrade quite reliably. But I had already tested it with Defender deactivated.<\/p>\n\n\n
<\/div>\n
adrian_ych:<\/div>\n
\nDid you run the Win11 upgrade as .\\administrator or at least an admin account ?<\/p>\n<\/blockquote>\n<\/aside>\n
I may not have said that clearly enough. Both the local installation with a mounted ISO and the installation via Windows Update work. Only the installation via WSUS does not always work. But sometimes it also works via WSUS. But the negative rate is then quite high.<\/p>","upvoteCount":0,"datePublished":"2025-03-01T08:31:29.197Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/10","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Cyberduck:<\/div>\n
\nI may not have said that clearly enough. Both the local installation with a mounted ISO and the installation via Windows Update work. Only the installation via WSUS does not always work. But sometimes it also works via WSUS. But the negative rate is then quite high.<\/p>\n<\/blockquote>\n<\/aside>\n
Sorry…Bro… coz sometimes we do get lost…thats why usually I would ask people to edit important into in main as well…<\/p>\n
WSUS even have known issues deploying the CUs and Feature Updates (LOL…cannot use shortform). I literally dropped WSUS 2 yrs back due to the CU & Feature updates.<\/p>\n
The stupid thing is that some updates that updates Intel chipsets and/or NIC sometimes cause the wifi to go offline (the satellite changes to a globe)…thus I deem WSUS also becomes very unreliable.<\/p>","upvoteCount":1,"datePublished":"2025-03-01T08:44:14.075Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/11","author":{"@type":"Person","name":"adrian_ych","url":"https://community.spiceworks.com/u/adrian_ych"}},{"@type":"Answer","text":"\n\n
<\/div>\n
adrian_ych:<\/div>\n
\nThe stupid thing is that some updates that updates Intel chipsets and/or NIC sometimes cause the wifi to go offline (the satellite changes to a globe)…thus I deem WSUS also becomes very unreliable.<\/p>\n<\/blockquote>\n<\/aside>\n
I don’t like the idea of having to migrate 130 Windows 10 PCs with sneakers.
What did you find in windowsupdatelog?<\/p>","upvoteCount":0,"datePublished":"2025-03-01T12:59:49.616Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/13","author":{"@type":"Person","name":"Rod-IT","url":"https://community.spiceworks.com/u/Rod-IT"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Cyberduck:<\/div>\n
\nI don’t like the idea of having to migrate 130 Windows 10 PCs with sneakers.
There is splashtop, teamviewer or even RDP<\/p>","upvoteCount":0,"datePublished":"2025-03-01T14:40:06.403Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/14","author":{"@type":"Person","name":"adrian_ych","url":"https://community.spiceworks.com/u/adrian_ych"}},{"@type":"Answer","text":"\n\n
<\/div>\n
adrian_ych:<\/div>\n
\nThere is splashtop, teamviewer or even RDP<\/p>\n<\/blockquote>\n<\/aside>\n
Yes, there is. The term sneaker network is a metaphor for doing things by hand that could be automated. If I perform the migration from the ISO, I have to coordinate with the users and so on. Similar problems arise with Windows Update. I would either have to go to the user’s workstation and initiate the update myself, or connect via RDP, which then logs the user out. Team Viewer is only installed for staff who also work from home. But there could be an alternative.<\/p>\n
If I could do this via WSUS, the migration would run in the background and the user would only have to expect an extended restart. They could do this when they leave home, for example. A simple note should then be enough. Then I also have to plan an intermediate step via 23H2 for the PCs with an Intel CPU before Gen 11, as a direct upgrade to 24H2 is not possible. There are a few. The project is complex enough, now Microsoft also needs to pee on my parade.<\/p>","upvoteCount":0,"datePublished":"2025-03-01T15:05:30.051Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/15","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Rod-IT:<\/div>\n
\nWhat did you find in windowsupdatelog[…]<\/p>\n<\/blockquote>\n<\/aside>\n
This:<\/p>\n
---snip---\n[...] 2025-02-26 13:13:17:681+0100 1 521 [AGENT_COMMIT_STARTED] 101 [...] Success Content Commit Commit Started: Windows has started committing the following update: Windows 11, version 23H2 x64 2025-02B \n[...] 2025-02-26 13:19:19:197+0100 1 522 [AGENT_COMMIT_FAILED] 101 [...] Failure Content Commit Commit Failure: Windows failed to commit the following update with error 0xc1900101: Windows 11, version 23H2 x64 2025-02B.\n[...] 2025-02-26 13:23:26:167+0100 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 [...] Success Content Install Installation Successful: Windows successfully installed the following update: 2025-02 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5051974)\n[...] 2025-02-26 13:23:26:198+0100 1 182 [AGENT_INSTALLING_FAILED] 101 [...] Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80242016: Windows 11, version 23H2 x64 2025-02B.\n---snap---\n<\/code><\/pre>","upvoteCount":0,"datePublished":"2025-03-01T15:07:12.830Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/16","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Cyberduck:<\/div>\n
\nWindows failed to install the following update with error 0x80242016: Windows 11<\/code><\/p>\n<\/blockquote>\n<\/aside>\nThis indicates something prevented the upgrade from completing, perhaps corrupt cache, an un stable network.<\/p>\n
At this point I would try one manually and see what errors you get. It may help.<\/p>\n
I would also check one of the failing machines for free space, not just on the C: drive but the recovery partition.<\/p>","upvoteCount":0,"datePublished":"2025-03-01T15:42:04.921Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/17","author":{"@type":"Person","name":"Rod-IT","url":"https://community.spiceworks.com/u/Rod-IT"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Cyberduck:<\/div>\n
\nYes, there is. The term sneaker network is a metaphor for doing things by hand that could be automated. If I perform the migration from the ISO, I have to coordinate with the users and so on. Similar problems arise with Windows Update. I would either have to go to the user’s workstation and initiate the update myself, or connect via RDP, which then logs the user out. Team Viewer is only installed for staff who also work from home. But there could be an alternative.<\/p>\n
If I could do this via WSUS, the migration would run in the background and the user would only have to expect an extended restart. They could do this when they leave home, for example. A simple note should then be enough. Then I also have to plan an intermediate step via 23H2 for the PCs with an Intel CPU before Gen 11, as a direct upgrade to 24H2 is not possible. There are a few. The project is complex enough, now Microsoft also needs to pee on my parade<\/p>\n<\/blockquote>\n<\/aside>\n
I think wsus was depreciated in 2024…<\/p>\n
I think thats why we also used PDQ deploy…we have 12000 machines in HQ alone…\n\n
<\/div>\n
adrian_ych:<\/div>\n
\nI think thats why we also used PDQ deploy…we have 12000 machines in HQ alone…<\/p>\n<\/blockquote>\n<\/aside>\n
With so many devices, you probably have completely different resources. It’s not comparable to us, I have to make it with what I have. And that is WSUS, especially as it is no longer being developed, but is still supported. We recently migrated the WSUS server to Windows 2022 and installed the latest version of WSUS, actually to avoid exactly these problems.<\/p>\n
In Intune, we also only have devices whose users have a Microsoft 365 license. All other devices, without Office for example, are only integrated in on prem AD. These are computers that support production, for example. That’s quite a lot, certainly a quarter of the entire infrastructure.<\/p>\n
But I don’t need to worry about that at the moment, not even about the introduction of further deployment software. As long as WSUS is officially supported, it won’t be possible to communicate this to the management, and it’s not my job either. I have to make it with what I have. It will be a matter of either solving the problem or starting to install it for everyone by myself.<\/p>","upvoteCount":0,"datePublished":"2025-03-01T16:42:55.871Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/19","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"}},{"@type":"Answer","text":"\n\n
<\/div>\n
Rod-IT:<\/div>\n
\nI would also check one of the failing machines for free space, not just on the C: drive but the recovery partition.<\/p>\n<\/blockquote>\n<\/aside>\n
So far, the manual installation has worked for every device where the installation via WSUS has failed. But I haven’t worked through that many yet. But the recovery partition is still interesting, this aspect is new to me.<\/p>","upvoteCount":0,"datePublished":"2025-03-01T16:46:29.197Z","url":"https://community.spiceworks.com/t/windows-10-migration-failed/1179608/20","author":{"@type":"Person","name":"thomaswildgruber","url":"https://community.spiceworks.com/u/thomaswildgruber"}}]}}
I have a problem with the migration from Windows 10 to Windows 11 23H2 via the WSUS. The update 23H2 x64 2025-02B (KB5051989) is published in the WSUS. The update is requested and the installation is performed according to schedule. The installation runs smoothly up to about 48%, after that everything is very fast. The update is displayed as installed and a restart is required. As expected, Windows reboots for the second time at 30% during the restart. However, the entire reboot process takes a good three quarters of an hour until the final cleanup. Until then, no error is displayed. After the restart, however, Windows comes up again with Windows 10. Without displaying an error message.
I let ChatGPT guide me through the analysis process and no error messages or suspicious entries were found in the Event Viewer. No evidence was even found that the system ever tried to install Windows 11.
Does anyone know what the problem could be here?
Please note: The system is capable for the upgrade:
PS C:\Windows\system32> \Windows\Temp\microsoft_windows11_readiness_script.ps1
{"returnCode":0,"returnReason":"","logging":"Storage: OSDiskSize=474GB. PASS; Memory: System_Memory=32GB. PASS; TPM: TPMVersion=2.0, 0, 1.38. PASS; Processor: {AddressWidth=64; MaxClockSpeed=2496; NumberOfLogicalCores=16; Manufacturer=GenuineIntel; Caption=Intel64 Family 6 Model 141 Stepping 1; }. PASS; SecureBoot: Capable. PASS; ","returnResult":"CAPABLE"}
5 Spice ups
Rod-IT
February 26, 2025, 2:00pm
2
I expect the event logs will have something.
Checked the Windowsupdate.log?
The CBS.log?
3 Spice ups
Damn, now the colleague has gone home with his laptop. But I was still able to try out part of your tip. Could it be that incompatible printer drivers during the migration (as described) are causing the problem? I would have found a few hints about this in the event log:
PS C:\Windows\SoftwareDistribution> Get-Content "C:\Windows\SoftwareDistribution\ReportingEvents.log" | Select-Object -Last 20
{72145CCE-E705-41C7-9522-725327A74EA5} 2025-02-26 13:19:19:197+0100 1 522 [AGENT_COMMIT_FAILED]
Commit Failure: Windows failed to commit the following update with error 0xc1900101: Windows 11, version 23H2 x64
(the list is much longer)
PS C:\Windows\SoftwareDistribution> Get-WinEvent -LogName "Microsoft-Windows-DeviceSetupManager/Admin" | Select-Object TimeCreated, Id, Message
e-iEet-oNae"irsf-inosDvcStuMnge/Amn"| eet-bjctTmCratd,Id Mssge
TimeCreated Id Message
----------- -- -------
26.02.2025 13:28:16 101 Der DSM-Dienst wird beendet. Die Betriebszeit des Diensts betrug 46 Sek...
26.02.2025 13:27:31 112 Das Gerät "AV44" ({00000000-0000-0000-ffff-ffffffffffff}) wurde verarbe...
26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container "{...
26.02.2025 13:27:31 112 Das Gerät "\\COMPANY-PS2\HLK Typenschilddrucker" ({f9a96989-3790-5512-8853...
26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container "{...
26.02.2025 13:27:31 112 Das Gerät "\\COMPANY-PS2\AV Kyocera P3055" ({d59f09e7-7253-5b7b-ab98-5b998...
26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container "{...
26.02.2025 13:27:30 130 Das Metadatenpaket "e4e3dd17-c038-47cb-a24c-78c36ffe0471" wurde für den...
26.02.2025 13:27:30 112 Das Gerät "\\COMPANY-PS2\IT Farbe" ({511014bc-cde8-5e97-a282-9290a38df1fc}...
26.02.2025 13:27:30 130 Das Metadatenpaket "38f6b193-c2df-4e1e-846d-244da079031e" wurde für den...
But now my test object has gone home. But we already suspect a certain printer, and we have exactly one department that doesn’t have this printer installed, so I’ll continue testing tomorrow.
Thank you very much, that was a good push in the right direction. Even if I don’t yet have confirmation that this is the problem, a driver or software problem fits the picture. The Windows 11 readiness script, of course, doesn’t look at anything like that, just the hardware details. The setup could actually only come across the problem during the installation and then perform a silent rollback. Sounds plausible…
Rod-IT
February 26, 2025, 3:46pm
4
If you’re using PowerShell like in your reply, I wouldn’t as you seem to be looking for specific, and in the wrong place.
Open Event Viewer and look under application and system for red or yellow warnings around the time of the last reboot. It’s easier to see issues in colour than it is trying to weed out the one you want in PowerShell, especially since you don’t know what you want at this point.
I’m not sure why you’re in software distribution either, that wasn’t something I suggested.
If you want to use PowerShell, you should run get-windowsupdatelog then view that.
1 Spice up
That’s my first rule of upgrading an OS, always see what’s installed and if it looks old, verify it is compatible before going through the lengthy process. Second rule is to temporarily disable antivirus for the process. Third rule is to cross my fingers.
2 Spice ups
somedude2
February 26, 2025, 11:05pm
6
e4e3dd17-c038-47cb-a24c-78c36ffe0471` is a cab file, and 0x80070490 says “That’s not what I wanted”
Are you sure you have the right install files?
adrian_ych
February 27, 2025, 6:09am
7
Cyberduck:
Damn, now the colleague has gone home with his laptop. But I was still able to try out part of your tip. Could it be that incompatible printer drivers during the migration (as described) are causing the problem? I would have found a few hints about this in the event log:
PS C:\Windows\SoftwareDistribution> Get-Content "C:\Windows\SoftwareDistribution\ReportingEvents.log" | Select-Object -Last 20
{72145CCE-E705-41C7-9522-725327A74EA5} 2025-02-26 13:19:19:197+0100 1 522 [AGENT_COMMIT_FAILED]
Commit Failure: Windows failed to commit the following update with error 0xc1900101: Windows 11, version 23H2 x64
(the list is much longer)
PS C:\Windows\SoftwareDistribution> Get-WinEvent -LogName "Microsoft-Windows-DeviceSetupManager/Admin" | Select-Object TimeCreated, Id, Message
e-iEet-oNae"irsf-inosDvcStuMnge/Amn"| eet-bjctTmCratd,Id Mssge
TimeCreated Id Message
----------- -- -------
26.02.2025 13:28:16 101 Der DSM-Dienst wird beendet. Die Betriebszeit des Diensts betrug 46 Sek...
26.02.2025 13:27:31 112 Das Gerät "AV44" ({00000000-0000-0000-ffff-ffffffffffff}) wurde verarbe...
26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container "{...
26.02.2025 13:27:31 112 Das Gerät "\\COMPANY-PS2\HLK Typenschilddrucker" ({f9a96989-3790-5512-8853...
26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container "{...
26.02.2025 13:27:31 112 Das Gerät "\\COMPANY-PS2\AV Kyocera P3055" ({d59f09e7-7253-5b7b-ab98-5b998...
26.02.2025 13:27:31 131 Fehler beim Staging von Metadaten. Ergebnis=0x80070490 für Container "{...
26.02.2025 13:27:30 130 Das Metadatenpaket "e4e3dd17-c038-47cb-a24c-78c36ffe0471" wurde für den...
26.02.2025 13:27:30 112 Das Gerät "\\COMPANY-PS2\IT Farbe" ({511014bc-cde8-5e97-a282-9290a38df1fc}...
26.02.2025 13:27:30 130 Das Metadatenpaket "38f6b193-c2df-4e1e-846d-244da079031e" wurde für den...
But now my test object has gone home. But we already suspect a certain printer, and we have exactly one department that doesn’t have this printer installed, so I’ll continue testing tomorrow.
Thank you very much, that was a good push in the right direction. Even if I don’t yet have confirmation that this is the problem, a driver or software problem fits the picture. The Windows 11 readiness script, of course, doesn’t look at anything like that, just the hardware details. The setup could actually only come across the problem during the installation and then perform a silent rollback. Sounds plausible…
Would you happen to have access to the Event Viewer (logs) ?
Then did you do the following
install latest firmware for all the hardware ?
run Windows update
remove installed AV and/or security software
1 Spice up
Yes, today I had another opportunity to analyze the system more closely, but apart from the two messages that the update was aborted due to the two error codes 0xC1900101 and 0x80242016, I did not find any other suspicious entries. At least not those that were not there before.
But I did discover something else that I would not have expected. During the whole upgrade process, another Windows 10 update was installed, which was probably not yet completed. Perhaps this is causing problems with the upgrade process.
---snip---
[...] 2025-02-26 13:13:17:681+0100 1 521 [AGENT_COMMIT_STARTED] 101 [...] Success Content Commit Commit Started: Windows has started committing the following update: Windows 11, version 23H2 x64 2025-02B
[...] 2025-02-26 13:19:19:197+0100 1 522 [AGENT_COMMIT_FAILED] 101 [...] Failure Content Commit Commit Failure: Windows failed to commit the following update with error 0xc1900101: Windows 11, version 23H2 x64 2025-02B.
[...] 2025-02-26 13:23:26:167+0100 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 [...] Success Content Install Installation Successful: Windows successfully installed the following update: 2025-02 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5051974)
[...] 2025-02-26 13:23:26:198+0100 1 182 [AGENT_INSTALLING_FAILED] 101 [...] Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80242016: Windows 11, version 23H2 x64 2025-02B.
---snap---
Beyond that, I can probably rule out my printer drivers as the cause. I have already successfully upgraded a device via WSUS first to Windows 11 23H2 and then to 24H2, and have reset it to Windows 10 with our default software. All GPOs are applied to the device as with the failed machine, and the user is also in the same groups as the user of the failed device, at least with regard to the printer installation. And this test ran without any problems as before.
So I can rule out a number of group policies and drivers. Of course, the test device is not exactly the same as the user’s device in terms of installed software etc. But my main concern in this test was the printer drivers, which I suspected the most.
So far, the Windows 10 update remains on the list of suspects.
Is there AV installed ?
adrian_ych:
Is there AV installed ?
Yes, Microsoft Defender Business. We usually leave it on because it actually recognizes the upgrade quite reliably. But I had already tested it with Defender deactivated.
I may not have said that clearly enough. Both the local installation with a mounted ISO and the installation via Windows Update work. Only the installation via WSUS does not always work. But sometimes it also works via WSUS. But the negative rate is then quite high.
Sorry…Bro… coz sometimes we do get lost…thats why usually I would ask people to edit important into in main as well…
WSUS even have known issues deploying the CUs and Feature Updates (LOL…cannot use shortform). I literally dropped WSUS 2 yrs back due to the CU & Feature updates.
The stupid thing is that some updates that updates Intel chipsets and/or NIC sometimes cause the wifi to go offline (the satellite changes to a globe)…thus I deem WSUS also becomes very unreliable.
1 Spice up
I don’t like the idea of having to migrate 130 Windows 10 PCs with sneakers.
Rod-IT
March 1, 2025, 12:59pm
13
What did you find in windowsupdatelog?
There is splashtop, teamviewer or even RDP
Yes, there is. The term sneaker network is a metaphor for doing things by hand that could be automated. If I perform the migration from the ISO, I have to coordinate with the users and so on. Similar problems arise with Windows Update. I would either have to go to the user’s workstation and initiate the update myself, or connect via RDP, which then logs the user out. Team Viewer is only installed for staff who also work from home. But there could be an alternative.
If I could do this via WSUS, the migration would run in the background and the user would only have to expect an extended restart. They could do this when they leave home, for example. A simple note should then be enough. Then I also have to plan an intermediate step via 23H2 for the PCs with an Intel CPU before Gen 11, as a direct upgrade to 24H2 is not possible. There are a few. The project is complex enough, now Microsoft also needs to pee on my parade.
This:
---snip---
[...] 2025-02-26 13:13:17:681+0100 1 521 [AGENT_COMMIT_STARTED] 101 [...] Success Content Commit Commit Started: Windows has started committing the following update: Windows 11, version 23H2 x64 2025-02B
[...] 2025-02-26 13:19:19:197+0100 1 522 [AGENT_COMMIT_FAILED] 101 [...] Failure Content Commit Commit Failure: Windows failed to commit the following update with error 0xc1900101: Windows 11, version 23H2 x64 2025-02B.
[...] 2025-02-26 13:23:26:167+0100 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 [...] Success Content Install Installation Successful: Windows successfully installed the following update: 2025-02 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5051974)
[...] 2025-02-26 13:23:26:198+0100 1 182 [AGENT_INSTALLING_FAILED] 101 [...] Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80242016: Windows 11, version 23H2 x64 2025-02B.
---snap---
Rod-IT
March 1, 2025, 3:42pm
17
This indicates something prevented the upgrade from completing, perhaps corrupt cache, an un stable network.
At this point I would try one manually and see what errors you get. It may help.
I would also check one of the failing machines for free space, not just on the C: drive but the recovery partition.
Cyberduck:
Yes, there is. The term sneaker network is a metaphor for doing things by hand that could be automated. If I perform the migration from the ISO, I have to coordinate with the users and so on. Similar problems arise with Windows Update. I would either have to go to the user’s workstation and initiate the update myself, or connect via RDP, which then logs the user out. Team Viewer is only installed for staff who also work from home. But there could be an alternative.
If I could do this via WSUS, the migration would run in the background and the user would only have to expect an extended restart. They could do this when they leave home, for example. A simple note should then be enough. Then I also have to plan an intermediate step via 23H2 for the PCs with an Intel CPU before Gen 11, as a direct upgrade to 24H2 is not possible. There are a few. The project is complex enough, now Microsoft also needs to pee on my parade
I think wsus was depreciated in 2024…
I think thats why we also used PDQ deploy…we have 12000 machines in HQ alone…
With so many devices, you probably have completely different resources. It’s not comparable to us, I have to make it with what I have. And that is WSUS, especially as it is no longer being developed, but is still supported. We recently migrated the WSUS server to Windows 2022 and installed the latest version of WSUS, actually to avoid exactly these problems.
In Intune, we also only have devices whose users have a Microsoft 365 license. All other devices, without Office for example, are only integrated in on prem AD. These are computers that support production, for example. That’s quite a lot, certainly a quarter of the entire infrastructure.
But I don’t need to worry about that at the moment, not even about the introduction of further deployment software. As long as WSUS is officially supported, it won’t be possible to communicate this to the management, and it’s not my job either. I have to make it with what I have. It will be a matter of either solving the problem or starting to install it for everyone by myself.
So far, the manual installation has worked for every device where the installation via WSUS has failed. But I haven’t worked through that many yet. But the recovery partition is still interesting, this aspect is new to me.
