Yeah, I read this! It was very useful! So yes, for sure IoT Enterprise LTSC and not Enterprise LTSC. I guess since I've been doing the normal Business Enterprise (non-LTSC), just wondering if there is a comparison for that. Like I am used to using KMS_VL_ALL_AIO .. so does that mean I should skip it? Thanks for that! Much appreciated your perspective (and expertise!) ^_^
@Enthousiast could you please check in your disk manager of your LTSC VM please ? In my disk manager, it tells me C: encrypted with BitLocker but in explorer it tells me the same as you, i can activate it in cmd as admin: when i do manage-bde -status i see encryption in progress
I don't think so, my disk manager doesn't say it's encrypted afaik it's encrypted by default on modern systems, mine is too old
Mine is a i7 11700 but also old now, check the video i added to the previous post. Earlier this year i bought a 12th gen laptop and it was not encrypted either till the owner forgot to uncheck an option and bitlocker and onedrive encryption were enabled and he sudddenly has an online account.
On elevated CMD i have this result C:\Windows\System32>manage-bde -status Volume C: [] [Operating System Volume] Size: 79.24 GB BitLocker Version: 2.0 Conversion Status: Encrypted Used Space Only Percent Encrypted: 100.0% Encryption Method: XTS-AES 128 Protection Status: Protection Disabled Lock Status: Unlocked Identification Field: Unknown Key Protectors: None Found so my disk seems to be encrypted but the protection is disabled & unlocked on my home compter running win10 IoT LTSC 2021 nothing is encrypted Volume C: [System] [Operating System Volume] Size: 930.36 GB BitLocker Version: None Conversion Status: Fully Decrypted Percent Encrypted: 0.0% Encryption Method: None Protection Status: Protection Disabled Lock Status: Unlocked Identification Field: None Key Protectors: None Found so the only way to revert to normal behavior on LTSC 2024 is on elevated CMD: manage-bde -off C: and the result is: Volume C: [] [Operating System Volume] Size: 79.24 GB BitLocker Version: None Conversion Status: Fully Decrypted Percent Encrypted: 0.0% Encryption Method: None Protection Status: Protection Disabled Lock Status: Unlocked Identification Field: None Key Protectors: None Found so i think it encrypt at installation by default on LTSC 2024
From my own testing, non-IoT 24H2 LTSC (in virtual machine) encrypts by default. 24H2 IoT (in virtual machine or bare metal) does not.
How can it be? I can see/change files mounted virtual machine or under winpe. If it is encrypted i should not do that.
nope, just use create_virtual_editions.cmd from uup-converter https://forums.mydigitallife.net/posts/1303176
Thanks. Already tried this method from your links in virtualbox. Thrown some error after changing default language so I gave up. Not a big fan of changing language on a working system. Always had some issues, internet is full of problematic stories as well. Don't mind en-US but many apps/search results sneakingly shows US results vs UK (always been a problem tbh)
Specifies the BitLocker status during upgrades. try this way setup.exe /BitLocker AlwaysSuspend AlwaysSuspend = BitLocker is always suspended during an upgrade.
Ltsc iot or ltsc are not avaible on uup dump ! On uup dump iot are similar to standard enterprise with windows store !"
please read first and understand next and then reply, the script can create IoT Enterprise 2024 LTSC when you feed it Enterprise 2024 LTSC in the desired language... Or just do it manually: Code: Dism /mount-wim /wimfile:install.wim /index:1 /mountdir:c:\mount Dism /Image:C:\Mount /Set-Edition:IoTEnterpriseS /channel:retail Dism /Unmount-Image /MountDir:C:\Mount /Commit and next (imagex is needed or wimlib imagex, this example is for imagex): Code: imagex.exe /flags "IoTEnterpriseS" /info "install.wim" 1 "IoT Enterprise 2024 LTSC" "IoT Enterprise 2024 LTSC"