Cumulative Update for Windows 11 Insider Preview (10.0.22635.3646) (KB5037858) Fails

I am out of the preview program and issue exists in the normal version of Windows 11 for Arm outside of preview as well.
 
TedM2 said:
P.S. I wonder if going back to straight up ARM instead of Insider Preview is a good call. Does anyone know how to do that?
Click to expand...
It won't make a difference - it's showing the same error with the normal ARM Windows release as well as Insider Preview. It's something that either Parallels or Microsoft have to fix; it seems there isn't much any of us can do other than not choose not to install that cumulative preview patch until things are resolved.
 
Just a tip. If you do not have your BitLocker keys, check https://account.microsoft.com/devices/recoverykey if you have Office 3655. Once you get past Bitlocker, you can disable it until they get this fixed; mine was repaired after I entered my keys. Then, you can pause updates until they get this fixed; it will still install virus updates but will hold off on cumulative updates.

After this is resolved, then you can re-enable Bitlocker.

If you do not have your Bitlocker keys, it is a lesson for the future to store them. However, even on a fresh install, at this time, this is happening. There is a major bug.
 
DavidS94 said:
Since updating Parallels this morning, I have been experiencing Windows Update issues with this preview. I have run the troubleshooter and SFC. Windows reports errors and that they have been successfully repaired.

Is anyone else experiencing issues with this update or has a suggestion on how to troubleshoot beyond the typical troubleshooter, SFC, and DISM steps?
Click to expand...

Same issue... running in circles... went twice through the bitlocker recovery process..... and finally made a snapshot to have a quicker way to get back on track
 
Another good tip - use Update Manager for Windows 1.1b on Github. On that page, just download the zip file, and use it - no installation. It's a simple little app that manages the Windows Update process for you.

It's been around a while, and it works great on Windows 11. Here is an article about it on TheWindowsClub for Windows 10, in the day.

I recommend this, because you can run it, hit the search button, and it will show you the KB5037858 download. You select it, hide it. Then, open Windows 11 Settings/Windows Update. Click "Pause for a Week". Then click "Resume Updates". Windows Update will run, process any other updates you may have, and you will not see the offending cumulative update! Windows Update is now clean, and you can easily get other updates and wait for the next cumulative update that fixes this.

****By the way, IMHO I think this is a Windows/MS problem. People not using Parallels have reported the same error(s) on other forums, and what some risky souls did was move to a newer build - Canary, Dev builds - and the problem is not there. Now, don't do that without thinking about it, as those builds are much less stable than the Beta build, and it's much harder to go back down to Beta build from them, vs. moving up to Dev/Canary builds. But it does offer some confidence that this could be fixed soon, even in the next update.

If you have not reported it on the Windows Insider Feedback Hub, please do so!!! The more that do, the higher visibility the problem has!
 
Don Awalt said:
@FrankO Please post a problem report on the Windows Insider Feedback Hub so MS is aware. This release is just broken. Thanks.
Click to expand...
Yes, it is broken. Ruined my two WIN 11 PRO VMs (standard updates, not insider). I have rolled back to either a snapshot or a backed-up prior VM file image, then used GPEDIT.MSC to make each update manual, *plus* disabled all updates for 7 days.

I have reported via the Microsoft hub, and will now also report it to Parallels.
 
Not sure why so many people want to address this to Microsoft... Out of curiosity I did install VMWare Fusion on my M3 MAX MacBook Pro and installed Windows 11 under VMWare then upgraded to the lastest MS update and... voila it did work just like that... So, as fas as I can see this is a 100% Parallels issue, not a MS issue.
 

Attachments

  • upload_2024-6-1_16-7-37.png
    upload_2024-6-1_16-7-37.png
    39.3 KB · Views: 20
I'm still asking whether anyone has run into this bug on Intel or if it is just happening on ARM processors.
 
Apple MacBook Pro M1 Pro Sonoma 14.5
Parallels Version 19.4.0 (54962)
Windows 11 Pro 10.0.22631 Build 22631 (*NOT* Insider Preview)

Unable to install 2024-05 Cumulative Update Preview for Windows 11 Version 23H2 for arm64-based Systems (KB5037853). Windows attempts a repair but still can't install KB5037853. Will open a support ticket with Parallels.
 
Same issue. Details listed below:

Apple M1 Max
Cumulative Update for Windows 11 Insider Preview (10.0.22635.3646) (KB5037858)
Edition Windows 11 Pro
Version 23H2
Installed on ‎2/‎7/‎2024
OS build 22635.3640
Experience Windows Feature Experience Pack 1000.22700.1013.0

Upon reboot, update installation fails and attempts automatic repair which then requests BitLocker key to continue. After entering key, automatic repair fails and changes are reverted and system boots correctly.
 
This was my reply today from the support ticket I created.


Hello,

Thank you for contacting Parallels Support.

Please note that we are aware of this issue, and it requires an investigation on a code level, thus we escalated it to the Development team.

The Development Team doesn't provide us with any ETA required for the investigation, thus we have nothing to share with you on this matter.

We hope it won't take a while.

But as soon as we get an update, fix, or any news regarding the case, we will update you no matter what this ticket state is.

Thank you once again for letting us know about this issue.

If you have any additional questions or need help, feel free to reply to this email.

Furthermore, we would suggest to change from Beta to the "Dev Channel", which appears to be more stable, simply by changing the channel in Windows / Settings / Windows Update / Windows Insider Program > Dev Channel.

Once we receive an update, we will reach out to you.

Have a nice day.

Best regards,
--
Saahir Joomun
Customer Support Engineer
||Parallels
 
MattC24 said:
Same issue. Details listed below:

Apple M1 Max
Cumulative Update for Windows 11 Insider Preview (10.0.22635.3646) (KB5037858)
Edition Windows 11 Pro
Version 23H2
Installed on ‎2/‎7/‎2024
OS build 22635.3640
Experience Windows Feature Experience Pack 1000.22700.1013.0

Upon reboot, update installation fails and attempts automatic repair which then requests BitLocker key to continue. After entering key, automatic repair fails and changes are reverted and system boots correctly.
Click to expand...

It is exactly what's happening to me
 
Dmitry@Parallels said:
Hi everyone, please accept my apologies for the delay in our response, I am very sorry about that.
Currently, our engineers are looking for the root cause of this issue. Rest assured, we will fix it as soon as possible.
Click to expand...
Thanks for the response Dmitry, do we have any indication of ETA as yet, my business requires BitLocker installed and so this is a significant blocker to all parallel users right now as they are showing compliance errors in our security team.
 
I am curious, does turning off BitLocker fix this so the update can be installed? That could be a lot safer than the recommendation to move to the Dev channel - that is a highly risky move and would likely require a fresh install to get back to beta channel!
 
zackc2 said:
This was my reply today from the support ticket I created.

Hi Zack,

This is terrible advice from a technical perspective. If you move to Dev you cannot move back to Beta or Release channels without a FULL clean install. I would push back on this suggestion as it is irresponsible of their support team to respond as such:
upload_2024-6-3_14-9-55.png
Click to expand...
 
I run Intel based Mac. Have been stuck on DEV Build 23620.ni since January 24th, 2024. Have reported it to both Windows Insider and to Parallels. No action whatsovever. I have tried installing via ISO - update/install still fails. Inaccessible boot drive is one of the most common errors, but have been getting other errors as well. VERY FRUSTRATING
 
Don Awalt said:
Another good tip - use Update Manager for Windows 1.1b on Github. On that page, just download the zip file, and use it - no installation. It's a simple little app that manages the Windows Update process for you.

It's been around a while, and it works great on Windows 11. Here is an article about it on TheWindowsClub for Windows 10, in the day.

I recommend this, because you can run it, hit the search button, and it will show you the KB5037858 download. You select it, hide it. Then, open Windows 11 Settings/Windows Update. Click "Pause for a Week". Then click "Resume Updates". Windows Update will run, process any other updates you may have, and you will not see the offending cumulative update! Windows Update is now clean, and you can easily get other updates and wait for the next cumulative update that fixes this.

****By the way, IMHO I think this is a Windows/MS problem. People not using Parallels have reported the same error(s) on other forums, and what some risky souls did was move to a newer build - Canary, Dev builds - and the problem is not there. Now, don't do that without thinking about it, as those builds are much less stable than the Beta build, and it's much harder to go back down to Beta build from them, vs. moving up to Dev/Canary builds. But it does offer some confidence that this could be fixed soon, even in the next update.

If you have not reported it on the Windows Insider Feedback Hub, please do so!!! The more that do, the higher visibility the problem has!
Click to expand...
Not sure why you're saying it's a Microsoft problem when Parallels has already acknowledged that it's a Parallels problem and a fix is underway...
 
You must log in or register to reply here.
Back
Top