Hello, We have a problem in our organization with the update KB5034439, this update doesn't appear in Windows Update configuration panel when accessing the machine but shows as pending in Azure Update Manager. The update was done two weeks ago, and daily automatic and manual assessments have been done on the machine since then. Any idea of what could be happening? There is another issue with this same update in others machines, but this case is more of a problem with the Windows Update itself. The update shows up in the Windows Update panel on the machines, even though those machines don't even have a WinRE partition (where the update is targeting). Also, when trying to run the update both from Azure Update Manager and locally on the server we get error 0x80070643. I need to solve these problems with this update, as it pollutes our Azure Update Manager dashboard with false pending updates. Thanks,

Hi @Tomeu Moreno Sitjar , Sascha Windrath , Pavel Fiala | ALVAO , Mikkel Leth , Juan Carlos Betancourt , This is a known issue and team is working on it. Current workaround is to add below mentioned registry value on systems where WINRE has been disabled or on devices with no WINRE. reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /f /v WinREVersion /t REG_SZ /d "10.0.20348.2201"

The July patch Tuesday has a fix for this issue. I was explained this after a few calls with MS for this specific issue. Since I applied the July LCU patch (KB5040437), I had to wait a day, as apparently the fix is not immediate (something that has to run), but since this morning, my Azure Windows 2022 test VMs do not see the KB 5034439 as required anymore. The LCU will be deployed widely on the weekend by Azure Update Manager.

Update KB5034439 should not appear as pending in Azure Update Manager.

Tomeu Moreno Sitjar 60

Hello,

We have a problem in our organization with the update KB5034439, this update doesn't appear in Windows Update configuration panel when accessing the machine but shows as pending in Azure Update Manager. The update was done two weeks ago, and daily automatic and manual assessments have been done on the machine since then. Any idea of what could be happening?
There is another issue with this same update in others machines, but this case is more of a problem with the Windows Update itself. The update shows up in the Windows Update panel on the machines, even though those machines don't even have a WinRE partition (where the update is targeting). Also, when trying to run the update both from Azure Update Manager and locally on the server we get error 0x80070643. I need to solve these problems with this update, as it pollutes our Azure Update Manager dashboard with false pending updates. Thanks,

Sascha Windrath 15 Reputation points

2024-02-27T10:16:47.7666667+00:00

Same here. Although I exclude it from the maintenance configurations it still shows as missing although it is not applicable to the Azure VMs. There is also no central place in Azure Update Manager where one could exclude updates centrally for all configurations.
Pavel Fiala | ALVAO 1 Reputation point

2024-02-27T12:51:02.2466667+00:00

Same problem here. Any advice?
Mikkel Leth 5 Reputation points

2024-03-01T14:02:35.3666667+00:00

Same Problem here. Although some machines in the same policy (None of our machines does run WinRE) does not have KB5034439 as pending. Its half of the vm's that report this update as pending.
Juan Carlos Betancourt 20 Reputation points

2024-03-06T14:28:09.4166667+00:00

The same for us. This KB5034439 and all similar ones that do not apply to Azure Virtual Machines must be automatically excluded in Azure Update Manager.

We also have the same comment about how to exclude KB in one place and not modify each existing maintenance configuration.

Accepted answer

tbgangav-MSFT 10,416 Reputation points

2024-03-06T16:05:49.27+00:00
Hi @Tomeu Moreno Sitjar, Sascha Windrath, Pavel Fiala | ALVAO, Mikkel Leth, Juan Carlos Betancourt,

This is a known issue and team is working on it. Current workaround is to add below mentioned registry value on systems where WINRE has been disabled or on devices with no WINRE.

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /f /v WinREVersion /t REG_SZ /d "10.0.20348.2201"
Please sign in to rate this answer.

10 people found this answer helpful.
Mikkel Leth 5 Reputation points

2024-03-07T11:34:30.2966667+00:00

Thank you. That solved my issues.

Saqib Sabir 0 Reputation points

2024-05-15T15:07:14.2166667+00:00

Thanks this resolved this for me as well, hope MS fix this long term for everyone.

Nadeem Bajaffer 0 Reputation points

2024-07-16T13:56:57.21+00:00

Thanks for the workaround. This has worked for me too.

Michael Trieu 0 Reputation points

2024-08-08T17:03:46.7466667+00:00

I am confused why this regkey fixes the issue. According to KB5034439:

IMPORTANT This update is not needed and will not be offered if your Windows Recovery Environment (WinRE) meets any of the following conditions: [...] If the WinRE image has a version greater than or equal to version 10.0.22000.2710. To determine the version of your WinRE image, check the WinREVersion registry value at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion.

Isn't "10.0.20348.2201" < "10.0.22000.2710"? Doesn't that mean KB5034439 would still be offered?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

1 additional answer

REICHERT Gilles (ENGIE IT) 10 Reputation points

2024-07-12T09:58:14.3233333+00:00

The July patch Tuesday has a fix for this issue. I was explained this after a few calls with MS for this specific issue.

Since I applied the July LCU patch (KB5040437), I had to wait a day, as apparently the fix is not immediate (something that has to run), but since this morning, my Azure Windows 2022 test VMs do not see the KB 5034439 as required anymore.

The LCU will be deployed widely on the weekend by Azure Update Manager.
Please sign in to rate this answer.

2 people found this answer helpful.
Ashish Pawar 15 Reputation points

2024-07-22T08:29:24.7566667+00:00

Hi @REICHERT Gilles (ENGIE IT) ,

We patched the LCU but still facing this issue in the Azure Update manager still persist to show as pending update, but whereas the internal check update does not show anything.

CSPX_a_VANISHA 0 Reputation points

2024-09-02T12:09:49.6533333+00:00

For me issue is not solved , i still the update error inside the machine and from update manager i get weird issue.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Update KB5034439 should not appear as pending in Azure Update Manager.

1 additional answer

Your answer