All right, thanks for the tips, what kind of CPU restrictions that cannot be bypassed? So, is it possible to convert regular IoT to IoT LTSC? WinNTSetup is better than use the regular installer?
I've checked my CPU instructions: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter vmmcall The only instruction that is missing is sse4.2...
POPCNT is part of SSE4.2 instruction set, so you can't run it it's not just some artificial limitation, and we can't recompile the kernel or anything else that requires it
But the interesting part is that the processor have POPCNT, but not SSE4.2... I thought that the bypasses tools could solve my issue... Thanks for sharing your knowledge and time for trying to help me!
That I guess so too, probably more extensions or processor instructions are tied on it. In my humble opinion, Microsoft using the power that they have, to throw in the trash as much as possible capable hardware as they can... I'm wondering about thin clients, that is usually in hardware matters, 15 years back if compared with PC's and Notebooks. The green movement is a bulls**t to Microsoft, produce more e-waste seems to be their goal now...
Dang! Avatar (game) and 24h2 (all, relax!) do not like each other, steam forums says no fix for the constant ctd(s) so far --- no medicine and doggie is a bit frustrated ... need other stuff do do know .....
rayman95 ask how to explain so why not help and explain for rayman95 how to do step by step with PowerShell.
OK; reverted back to my 2021 IoT >>> backup: 1. Juli and now restored back ---- AVATAR runs perfectly .... 2024 IoT ..... erratic CTDs with no debug* .... ... is on hold ---- FLAWED....
WHY???? . MSDN-ISOs will come (if ...) is still BETA! IoT is en-US only always ... MSDN brings langs (all indices still included ). If Inplace-Upgrade is goal, you need to switch lang in Settings first ... REBOOT ... than change values (Install(!!!) and System language to en-US. I posted them, others before ... hope someone might hin .
is Windows 11 IoT Enterprise LTSC 24H2 OEM activate-able with KMS or what version is need to make it run full, forever? I would like to give a try.
Windows 11 IoT Enterprise LTSC 24H2 OEM est activé avec HWID (Digital License) Method to Permanently Activate Windows or if it is not activated using the activation tool from massgrave the one that is not activated is Enterprise LTSC 24H2 if you activate with the HWID tool from massgrave it converts it to Windows 11 IoT Enterprise LTSC 24H2.