Yep, they definitely messed up but I'm still glad I directly received the "fixed" update directly through WU on my IoT Enterprise LTSC
@Enthousiast WU finally gave me KB5063060 today (June 11) around 12:45 pm . It was also able to install and restart successfully.
There is just one release of LTSC in all languages, at the OP of this thread you can find the download options: https://forums.mydigitallife.net/posts/1854338
If you meant as described here https://forums.mydigitallife.net/th...2024-24h2-26100-x.88280/page-120#post-1859557 yes, obviously, it"s much easier but I prefer using original IoT LTSC edition for installation.
"coz, AFAIK, there is some difference between original and converted IoT LTSC. https://forums.mydigitallife.net/th...2024-24h2-26100-x.88280/page-130#post-1869012 In principle, that"s a matter of choice...
Anyway I just shared Powershell localization algorithm I found for those who prefers installing original IoT LTSC. I do not call up anyone to follow... And no need to convince me. Eventually the PID.txt pasting method is also my post. I think people must always have the choice...
Hi Team. It's been a while but I let both of my Test Laptops sit for a few weeks after OS and basic programs install. I played around with them from time to time, and they seemed fine. Today I went to see how they'd handle Windows Update, and new Defender files. The Asus laptop with Windows 11 Enterprise LTSC 2024 updated and works just fine. But the MSI with Windows 11 IoT Enterprise LTSC 2024 after updates and rebooting came back with an error code under Activation State. In RED it said " Windows reported that no product key was found on your device. Error Code: 0xC004F213 " MS Office also said it wasn't a legitimate key. I used Microsoft Activation Scripts v3.1 Portable to repair them both and both seem to be working fine now. I'm assuming the previous KMS effort timed out, but I could be wrong. Do you have any idea what could cause this? Thanks for the assist. I'm learning a ton.
W10UI_10.52 Code: Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.26100.1742 Processing 1 of 2 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9310.1 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_KB5059093~31bf3856ad364e35~amd64~~26100.3907.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.4351.1.0 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x80070306 Error: 774 One or more errors occurred while processing the request. The DISM log file can be found at C:\windows\Logs\DISM\DismLCU.log