So let's talk about this issue. However, my starting position is different. I have Nokia Lumia 2520 with Qualcomm MSM8974 Snapdragon 800 (28 nm). I also carefully avoided the golden-key MS perma-fix, so I am basically stuck on the latest safe cumulative update KB3192404 (CU-2016-October-Preview), with WU-AutoUpdateDisabled: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update] "AUOptions"=dword:00000001 "CachedAUOptions"=dword:00000001 "ElevateNonAdmins"=dword:00000001 "ForcedReboot"=dword:00000002 "IncludeRecommendedUpdates"=dword:00000001 But now, when we have reached the Final-Cumulative-Update (KB5022352-CU-2023-January), we can probably do more. The golden-key MS perma-fix, which spoils the device, resides in EFI files: bootarm.efi boot.efi bootmgfw.efi ...(maybe not in all of them, but we need all 3 files with the same version probably.) So, while it is not safe to install KB5022352-CU-2023-January "online" within WRT81, it has to be "pretty safe" to: 1. Create custom installation media (USB, FAT32). 2. Integrate KB5022352-CU-2023-January into it. 3. Replace all-new EFI files with old ones (in C:\Windows\Boot\EFI... and even C:\Windows\WinSxS\...) (The old EFIs are from 2016-08-13.) 4. Apply install.wim to device in WRE (dism /apply-image /imagefile:O:\sources\install.wim /index:1 /applydir:W:\) 5. Fill ESP partition in WRE (bcdboot W:\Windows /s S: /f UEFI) 6. 2nd (redundant) check if the correct EFI files are stored in S:\EFI That should be safe. So now, we can talk, about if using your solution, would be even safer: 1. It does need to be ported to MSM8974 probably. 2. Is the golden-key MS perma-fix killed in your EFI files (= are they newer than 2016-08-13)? 3. Are you the 2nd guy, who has released the golden key policy with LH? You have a similar avatar on GitHub as him.
Hello again. I have a question about the BitLocker trick. Re: reboot back to WinRE (from manage-bde processing?) Whole WinRE is stored on RAMdrive, so when I will reboot, doesn't the value in the registry get lost? How about letting manage-bde to encrypt in the background, then access the registry (or do I even need to disable BitLocker 1st too, so: then quit BitLocker a then access the registry)? Q: When my whole C: drive is already encrypted, do I need to decrypt it 1st or is there another shortcut? Is there any chance, that you will just get an old Lumia 2520 from China for just something like 50 USD and test it yourself then re-release the thing for it? If so, I could donate the bucks, if it will not be too expensive. Ah, good to know. Too bad that both french guys (LH and Owl) are just dicks, who rather block people instead of talking with them. LOL Thanks. It has installed fine. How did you find it? It isn't present in the catalog. Are there any other arm32 updates BTW? BTW: There is another mistake from MS: all arm32 updates of the DotNET CU type: 20xx-xx Security and Quality Rollup for .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Embedded 8.1 and Windows Server 2012 R2 (KBxxxxxxx) ...are published in the catalog (even for WRT81).
I am very much tempted to make a new custom ISO with all arm32 updates (and old EFIs to protect the jailbreak). Is there anyone, who wants it too? So updating of W8-1 continues, let's watch it by one eye: 2023: January: 2023-01 Security Monthly Quality Rollup for Windows 8.1 (KB5022352) February: 2023-02 Servicing Stack Update for Windows 8.1 Embedded (KB5022922) 2023-02 Security Monthly Quality Rollup for Windows 8.1 Embedded (KB5022899) 2023-02 Security and Quality Rollup for .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Embedded 8.1 and Windows Server 2012 R2 (KB5022733) March: 2023-03 Servicing Stack Update for Windows 8.1 Embedded (KB5023790) 2023-03 Security Monthly Quality Rollup for Windows 8.1 Embedded (KB5023765)
Offtopic: How I can get rid of the redirection from IE to Edge (in W11 b22623.1413)? (I have restored ieframe.dll, inetcpl.cpl + MUIs and MUNs, so IE runs and displays, but any URL written to its address bar just starts Edge.)
Scan dump of WU revisionIDs (GetExtendedUpdateInfo) it's the last win8.1 arm update, yet .NET updates are the only updates that get published in WSUS for Win 8.1 RT i guess their team have different decision than Win updates team
I love you all (en bloc). <3 It works. Now let's examine your other projects on GitHub. I still need WRT81 to be able to autostart programs (StartUp folder and Run reg key). Maybe you can code me a system service, which will do that or somehow track and restore the original autostart mechanism by some hack. What a nice SEXY red Lumia you have. It is a 1st class Raptor. And you are pretty clever for sure, so don't talk bad about yourself. Pls, monitor it. Maybe you can tell me something else: I have 3 W11 b2262x PCs all in RP Insider ring, and on one I can install (PSFExtractor, DISM) both Moment0 (like .1413) and Moment3 (like .1391) updates just fine. On the other two, I can install only Moment3 (like .1391) updates and DISMing Moment0 update fails (missing files, components not found). Why it is like this?