Windows 10 Version 22H2 (KB5022834) will not update

I agree with all you said. I want to add that I (and I guess everybody else here) actually paid money for this OS, which now, intentionally or by incompetence, is unusable. This exact same problem is reported by hundreds, probably thousands of people, since what? Six months? Microsoft does not seem to care at all, there is still no fix, not even an attempt to fix it. I'm not a beta tester for Microsoft and have better things to do in my life than trying to flip bits in the registry, delete, modify or touch some random files, hoping to magically fix a broken update. It might be a coincidence, but this one computer has a reduced internet speed as well, while all other systems do not. What is this? A try to "motivate" me to "update and restart"?!?!?! Do watch the update install and then undo everything for about half an hour?

That being said: is there a lawyer here that is interested in starting a class action lawsuit against Microsoft? I'm fed up and I'm happy to join.

please help me to update my pc

Hello Ian,

I am seeing the same thing you are in my CBS log regarding AMD., Makes no sense why an update being sent to an Intel based processor Windows 10 would try installing AMD64.

My Windows update is paused currently. The following lines show up in the CBS log file from today at boot-up.

2023-02-24 10:00:18, Info CBS Loaded Servicing Stack v10.0.19041.2300 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2300_none_7e14edbc7c88b7d5\cbscore.dll

2023-02-24 10:00:18, Info CBS Build: 19041.1.amd64fre.vb_release.191206-1406

I see Ian has a new thread started to investigate this. I will keep my eye on both of these threads moving forward.

Hi Guys,

I also have been trying to troubleshoot this issue and came across the following error entry within the CBS.log file.

*2023-02-24 14:31:05, Error CSI 000000ae (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #2535422# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-AppManagement-UEV-WOW64-Deployment, version 10.0.19041.1706, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-AppManagement-UEV-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1706.d5d73e1702212498fc2ec00c95787681', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = [gle=0x80073701]*I agree with IanJ_1 on this one that the package appears to be built on AMD64 architecture as opposed to X64, which I suspect is the issue here. If you require any additional information that may prove useful, then please reach out.

I have a fulltime job, including week-ends, have no time to manipulate Win all the day. I'll try if I have a bit time, but for now no time. An OS is supposed to be functional, that's the sense of "operating" system in OS. Sorry to remind that. ;)

I have a full-time job also, and that's configuring/deploying Windows. And I volunteer the rest of my time here. Practically, we as end-users can do nothing to improve the Windows setup experience (other than send your feedback via the FBH). That said, fixing/tinkering the OS is the only option left if you want to avoid reinstalling Windows.