Thanks @moderate for always posting the new links. (KB4586085 was released before and did not change)
Good morning all. Total noob here. I have a Surface RT with Windows 8.1. I would like the past in windows 10, with a simple tutorial if possible Big thank you to you Luis
Because W10 arm64 (21H2Prev to be exact) now have "shared arm64-x64 profile" (can install and run x64, PEs (EXEs and DDLs) are both arm64+x64 in one file) (2nd profile is arm32 and 3rd x32) and MS distributes all updates according to this scheme now: For example: Microsoft D3DMappingLayers v0-2011-3-x0 Files applied on every W10 arm64: Microsoft.D3DMappingLayers_0.2011.3.0_arm64__8wekyb3d8bbwe.appx Microsoft.D3DMappingLayers_0.2011.3.0_arm__8wekyb3d8bbwe.appx Microsoft.D3DMappingLayers_0.2011.3.0_x64__8wekyb3d8bbwe.appx Microsoft.D3DMappingLayers_0.2011.3.0_x86__8wekyb3d8bbwe.appx
BTW: In W10 arm64 21H2Prev there is also a bunch of another huge changes: DotNET Framework and Windows PowerShell v5-1 now run 64bit (but nobody know, if arm64 or x64), while earlier it runned under x32 emulation. For example: Your C2R-R2V now fails to detect x32 Office installed in W10 arm64 21H2Prev (BTW2: x64 Office C2R MS's installer still not support 21H2Prev.), but C2R-R2V succeeds to detect x32 Office installed on W10 20H2 RT. Your friend @Windows_Addict tried to investigate why. It is BTW real problem, now there is no tool for W21H2Prev to convert Retail lic to Volume other way, than upgrade from W20H2 RTM.
I know since both arm64 & x64 share the same 64-bit binaries (system32 files), this seems the only way for batch scripts to differentiate (credits @Windows_Addict) Spoiler Code: @setlocal DisableDelayedExpansion @echo off :: Re-launch the script with x64 process if it was initiated by x86 process on x64 bit Windows :: or with ARM64 process if it was initiated by x86/ARM32 process on ARM64 Windows if exist %SystemRoot%\Sysnative\cmd.exe ( set "_cmdf=%~f0" setlocal EnableDelayedExpansion start %SystemRoot%\Sysnative\cmd.exe /c ""!_cmdf!" %*" exit /b ) :: Re-launch the script with ARM32 process if it was initiated by x64 process on ARM64 Windows if exist %SystemRoot%\Windows\SyChpe32\kernel32.dll if exist %SystemRoot%\SysArm32\cmd.exe if %PROCESSOR_ARCHITECTURE%==AMD64 ( set "_cmdf=%~f0" setlocal EnableDelayedExpansion start %SystemRoot%\SysArm32\cmd.exe /c ""!_cmdf!" %*" exit /b )
Yes, we spent two hours on that with @Windows_Addict on Discord. So you can update C2R-R2V. BTW: 2020-10 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6...7.1, 4.7.2, 4.8 for Windows 8.1 RT for ARM-based Systems (KB4579979) ...is now "satisfy WU" on WRT8-1 no matter, which DotNET FW version is installed. Dunno why. On my DotNETFW_v4-8 it installs windows8.1-kb4578976-arm-ndp48_ffe...315.cab for reason unknown.
how exactly it fail to detect x32 Office on W10 arm64 21H2Prev? it don't detect its existence? or fail to convert?