Action on applicable devices to this fixlet 5059607: Dynamic Update for Windows 10 Version 22H2 - Windows 10 Version 22H2 - KB5059607 (x64) is failing as WinRE version is not upgrading even after the script completion. Tried applying Update WinRE version to Registry for Safe OS dynamic updates as prerequisite but still failing. Any suggestions?
Welcome to the forums.
Did you get an error code?
I can’t find that fixlet in my content, which site is it in?
@Phoenix, what is the output of the following command line from this endpoint that is failing:
reagentc.exe /info | findstr /r /c:"Windows RE [status|location]"
You should have “Windows RE status: Enabled” as an output, correct?
Furthermore in QNA, what is the value returned from this client relevance:
values "WinREVersion" of keys "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" of native registry
This value returned is most likely less than “10.0.19041.5847”.
-Gus
Hi @D.Dean,
Thanks for the response.
Site - Patches for windows
Error - Multiple exit codes (13, 18 and 23)
Hi @gus,
Thanks for the response.
Getting this value for registry 10.0.19041.1.
Thanks. Second time in the past 7 days where I searched at the root and did not find it, but search the site and do.
I am getting a failed, even though every line ran and the exit code is 0. Digging in some more.
Hi @D.Dean,
Thanks for the response.
Looking for your insights.
can you check the log and see what the results were?
Mind show error 32 while executing the dism command.
Everywhere I search, Error 32 for DISM shows that the command mounted to “X:” instead of “C:” but the command below checks for the mount, so I am not sure what is happening.
concatenation of (pathnames of root folders of drives of windows folders; "\mount")
AI Overview…
A DISM (Deployment Image Servicing and Management) error 13, also known as “!ERROR=13 - Improper File/Device Address”, typically indicates an issue with accessing a file or device, such as a missing file, incorrect permissions, or an attempt to load a non-program file incorrectly. To resolve this, you can try updating your ADK, re-capturing the image, or deploying a vanilla Windows image. You can also attempt a cleanup using the DISM command /StartComponentCleanup.
I just ran this fixlet against 2 different endpoints and it successfully worked in my environment. I would really like to understand the differences preventing this fixlet from successfully running in your deployment.
We are following the guidance from Microsoft as described in this article to “Add an update to the Windows RE” image:
Perhaps you can attempt to perform these commands described in this article on your endpoint to obtain further insight on the root of the problem.
Thanks, Gus.
P.S. Review the specific section of the article that states “Apply the update to a running PC”
Hi @D.Dean,
Thanks for the response and help.
Hi @gus,
Thanks for the response and help.