Can anyone help with this error " event id 2545 Error concerning MDM Declared Configuration: Function (checkNewInstanceData) operation (Read isNewInstanceData) failed with (The parameter is incorrect.) " In event viewer, I looked at Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider and noticed that the error under Admin always happens between Information events under Operational, specifically after "DcSvc: Service status updated. Current state:" (0x2) and (0x4) yet before (0x3) and (0x1)
Weird, you say. I checked my ISO store and unfortunately I have multiple editions of LTSC: 2 shown for example en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso en-uk_windows_10_enterprise_ltsc_2019_x64_dvd_723dfbc1.iso (this one was an svf conversion) I have no idea which ISO I used the last time I clean installed. Perhaps you might suggest a version that would be suitable - one that isn't weird settings>System>about suggests 19044.2251 is the version rather than winver's .251 - this may have been a bad paste by me.
= 2021 LTSC = 19044.1288 = https://forums.mydigitallife.net/th...1-22h2-vb_release.80763/page-439#post-1705312 = 2019 LTSC = 17763.316 = https://forums.mydigitallife.net/th...prise-n-ltsc-2019.76325/page-164#post-1508318
If I wanted to try with an in place upgrade using en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso would the set up mechanism recognise the current weird (IoT) Enterprise started with 19044.1288, so .251 is a very weird delta build nr for the OS) install as a viable candidate for an upgrade?
You can simply try, mount ISO and run setup.exe and see what happens. Inplace upgrades don't mind if the used ISO is of a lower delta build (the stuff after the 19044....).
@summersuns, you replied within the code tags inside the quote. Probably it's the linux/windows dual boot scenario causing this.
So I installed using en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso, pretty sure I selected IoT Enterprise during installation, and then activated using KMS_VL_ALL_AIO-48. Now in Settings -> System -> About, I see Windows 10 Enterprise LTSC. How do I check if IoT Enterprise version has been installed? Or did KMS_VL_ALL_AIO-48 change it to non-IoT with only 5 years support? Sorry new to this.
If you want to activate IoT Enterprise LTSC you must use a HWID based activator like Microsoft Activation Scripts (MAS).
Anyone started getting bsod ? Since I didn't change hardware nor software I think maybe the latest update, kill my system, 2 bsod in 1-2 days ? Weird
Yesterday i picked up a 19045.2364 Home laptop and it can't boot anymore right after the update installed (stopcode bsod and no known fixes worked) but when i insert an usb key the uefi bios freezes too so i think this laptop has more problems. After a lot of trying i got a clean install of 19045.2364 on it and now it runs fine.