So I have solved pretty much all the issues I've had with NTSC except these few: 1. CloudStorage errors on boot: Code: Microsoft-Windows-CloudStore Error 0x80070422 occurred. See event details for more information. This appears to be an Explorer-related s**t: Code: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudStore but I havent figured out what causes it. Deleting it resets your start menu customization and that's about it. 2. SettingsSync on boot Code: shell\roaming\settingsync\explorersettinghandler.cpp(<number>)\SettingSync.dll!00007FFCE1CE969A: (caller: 00007FF7D90FFA49) ReturnHr(4) tid(1058) 80070002 The system cannot find the file specified. SettingSync.dll is loaded dynamically by both User Profile Service and Explorer. I went through all possible options in Explorer and all possible policies in GPO related to sync and disabled them all yet it still happens no matter what. Dead end as well. 3. Thousands of errors per day for WMI/DAPI s**t like this: Code: Microsoft-Windows-Crypto-DPAPI "DPAPI Unprotect failed . Status: 0x8009000B ReasonForFailure: Could not get the master key" Microsoft-Windows-Crypto-DPAPI "Master key access failed. GUID: {e49edec0-f1f7-4167-84d4-4b08c6f5e071} Success: false Last error: 0x0 Master key disposition: 0x0" or this Code: Id = {4320A058-2BD9-49EF-8426-B39B9B4EC723}; ClientMachine = DESKTOP-RE487UR; User = NT AUTHORITY\SYSTEM; ClientProcessId = 2576; Component = Unknown; Operation = Start IWbemServices::DeleteInstance - Root\Rsop\Computer : RSOP_ExtensionStatus.extensionGuid="{FC491EF1-C4AA-4CE1-B329-414B101DB823}"; ResultCode = 0x80041002; PossibleCause = Unknown Piles up in hundreds and thousands per day. It is very much possible it just typical Winblows junk but it just annoying. ------- Other than that LTSC is running smoothly for me so far.
Hmmm the untouched x64 LTSC 2021 and custom image built with DISM w/ applied patches will fail "sfc /scannow" after first boot. I scanned over CBS.log but I couldn't find the specific issue it seems to be unhappy about. *Edit* This appears to be an issue on all 21H2 releases, I tested the "consumer" Pro/ProN versions and the result was the same... running "sfc /scannow" or "sfc /verifyonly" will return "Windows Resource Protection found integrity violations", but I can't anything in CBS.log beyond some warnings about NTFS ACL's.
Does this 21H2 still pings idle secondary HDDs every 8-10 minutes? Is a thing with 1809 I can confirm but some say it wasn't like that with 1607 which I can't confirm. And there wasn't a single 3rd-party background program running if you are wondering for the 1809.
I think I did something similar with 1809 and it worked... What do you all think about the "tee vee" YouTube channel method of converting SAC (or GAC as its called nowadays) to LTSC which just copies and registers the EnterpriseS .xrm-ms license files on C:\Windows\System32\spp\tokens\skus folder to the Enterprise installation and adds the LTSC KMS key? The goal being just having LTSC SKU (I assume no feature updates) with full Enterprise image content (appx, restricted codecs, etc.). You could just add the classic calculator package from LTSC and everything will be complete (OCD I am I must admit...).
I still don't get your point all 17763 images will have Code: 17763.1.amd64fre.rs5_release.180914-1434 Server 2022 Code: 20348.1.amd64fre.fe_release.210507-1500 logically, all 19041 images (including EP variants 19042/19043/19044) will have Code: 19041.1.amd64fre.vb_release.191206-1406 the value don't change regardless updates
Excuse my English, but I am using google translator to post this query. Is there a way to pass the enterprise Iot version to Spanish language? What is the correct activation method for this version? Thank you very much for your answers.
Can I use IoT version for desktop, laptop because support is longer? Thanks. PS: Should I switch to this version if I'm on the LTCS 2019 version?
Search this in the OP: Code: [02] 06/10/2021 en-US x64 10.0.19041.1288 Windows 10 Enterprise N LTSC | EnterpriseSN