Forum Discussion
b26052 - WORKAROUND - no offer to upgrade via Microsoft Update from b26040
Hi everyone,
is it just me? I would have expected the second time to upgrade to the latest build via Microsoft Update. But it won't appear when searching for updates.
cannot report in feedback hub, as it's spinning circles as soon you try access "feedback"
logoff / login doesn't heal.
WU Log attached.
Workaround (Thank you to the community):
- Windows + I > Windows Updates > Windows Insider Program
- Set channel from Release preview to Canary
- Release Preview is then greyed out
- Search for updates again.
- Error was that the Windows Insider Program level was changed to "Release Preview" even though I set it to Canary since the beginning, so after set it correctly back to Canary the upgrade was correctly offered in Windows Update
6 Replies
- Error was that the Windows Insider Program level was changed to "Release Preview" even though I set it to Canary since the beginning, so after set it correctly back to Canary the upgrade was correctly offered in Windows Update
- I'm having the exact same issue
You may not search for Windows Updates because of the lack of update channels. You can download the new ISO, mount it, and then run the setup.exe. This problem has appeared since early 2022, when the first Windows Server with Windows 11 UI appeared.
Also, the feedback hub isn't working properly, because it is missing essential packages from the Microsoft Store - which is not available in any edition of Windows Server. You may need to install these packages within the Store. Hope that will be fixed in the next release of Windows Server 2025.
Missing packages you may need:
Microsoft.NET.Native.Framework.1.6_1.6.27413.0_x64__8wekyb3d8bbwe.Appx Microsoft.NET.Native.Framework.1.7_1.7.27413.0_x64__8wekyb3d8bbwe.Appx Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe.Appx Microsoft.NET.Native.Runtime.1.6_1.6.24903.0_x64__8wekyb3d8bbwe.Appx Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe.appx Microsoft.UI.Xaml.2.0_2.1810.18004.0_x64__8wekyb3d8bbwe.Appx Microsoft.UI.Xaml.2.1_2.11906.6001.0_x64__8wekyb3d8bbwe.appx Microsoft.UI.Xaml.2.4_2.42007.9001.0_x64__8wekyb3d8bbwe.appx Microsoft.UI.Xaml.2.7_7.2208.15002.0_x64__8wekyb3d8bbwe.Appx Microsoft.UI.Xaml.2.8_8.2212.15002.0_x64__8wekyb3d8bbwe.appx Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe.Appx Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe.appx- I am experiencing similar symptoms in my environment.
It seems to be occurring when Opt-In is done with a version before 26040, or the Ring is only in Release Preview.
If the Server's Registry settings are different, I would like MS to release them. - my version of Server did see an update, although WU wanted to install a version of Windows 1!
- I believe the wrong displyname is a known issue, wasn't it named in the release notes?
