You all make it like an "inside game", instead of just making things EASY and CLEAR. ================= Ok, so I'm trying en-us_windows_10_business_editions_version_21h2_updated_jan_2022_x64_dvd_0b69c5ac.iso now - in-place upgrade
just jumping in, but I believe he highlighted arm64 because unless your cpu has a arm64 architecture (just google your cpu to find out) then the update you downloaded wont work. More than likely you would need the x64 download.
Well the install of en-us_windows_10_business_editions_version_21h2_updated_jan_2022_x64_dvd_0b69c5ac.iso ALSO failed
@DeathStalker77 Since you're cross-posting in multiple threads, let's start straightening things out. What machine are you currently "experimenting" on? More specifically what processor you have and what is your current OS(version and architecture).
Processor Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz 3.60 GHz Installed RAM 64.0 GB System type 64-bit operating system, x64-based processor Edition Windows 10 Pro Version 21H2 Installed on 10/11/2020 OS build 19044.1348 Experience Windows Feature Experience Pack 120.2212.3920.0 Feature Updates Update to Win10 v21H2 successful on 12/06/2021 Update to Win10 v21H1 successful on 06/27/2021 Update to Win10 v20H2 successful on 11/14/2020 Quality Updates 2022-01 Cumulative Update for Windows 10 Version 21H2 for x64-based systems (KB5009543) Failed to install (0x800700c1) 2022-01 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5010793) Failed to install (0x800700c1) C:\Windows\system32>sfc /scannow Windows Resource Protection could not start the repair service. C:\Windows\system32>DISM /Online /Cleanup-Image /CheckHealth Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.1348 The component store cannot be repaired. The operation completed successfully. C:\Windows\system32>DISM /online /cleanup-image /startcomponentcleanup /restorehealth Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.1348 Error: 193 %1 is not a valid Win32 application. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Windows 10 (consumer editions), version 21H2 (updated Jan 2022) (x64) - DVD (French) fr-fr_windows_10_consumer_editions_version_21h2_updated_jan_2022_x64_dvd_08898a9c.iso SHA256 : 4778411190bb1522f3f24236ff6609e4bf688002d69b2e09f9a0798c3687962e release date : 2022-01-18 Windows 10 (consumer editions), version 21H2 (updated Jan 2022) (x86) - DVD (French) fr-fr_windows_10_consumer_editions_version_21h2_updated_jan_2022_x86_dvd_872cbafa.iso SHA256 : a8a329bdc12ff4483d830c4d2db809afc4c16893609ea85a843c67bf67623edb release date : 2022-01-18 Windows 10 (business editions), version 21H2 (updated Jan 2022) (x64) - DVD (French) fr-fr_windows_10_business_editions_version_21h2_updated_jan_2022_x64_dvd_92acbfa4.iso SHA256 : 1e462d425387101bd5a34b7ec7b82b0a61c9f81adadeb3509c1d9e15b7ce852f release date : 2022-01-18 Windows 10 (business editions), version 21H2 (updated Jan 2022) (x86) - DVD (French) fr-fr_windows_10_business_editions_version_21h2_updated_jan_2022_x86_dvd_87586677.iso SHA256 : 44aad893aeb4673f2a08564b46d6cef7dc56b7f5acdfaa3d0db5097a29cfe67d release date : 2022-01-18
Seems you have used so much time and no luck installing, take a rest and do a clean install, but back your most importing stuff yuo have, I would not my self use that much time fixing that problem the only way is Clean install.
Maybe write a full 50-page report while he's at it. There's no point. That machine needs a clean install.
yup and DS77 should stop posting here until he has fully done a successful clean install I'm already thinking the RP updates will get revised or be re-released to include the vpn fixes
I think the "D" non security updates (this week) will replace all. And my remark was about the UEFI problems, 1.5 weeks later we know that MSFT didn't cause them and so they won't fix it.
"we know that MSFT didn't cause them? "? How do you (we) know that? & if not MSFT, then what's the cause? Did I miss something in-between this 1.5W?