Search results

Thank you, nothing in that preset should break shutdown. Best would be to proceed with the Host Refresh fix, using the latest NTLite, unedited ISO + same preset + latest updates.

That is normal for command-line, as far as I know. You can use start /WAIT "" "ntlite command here" Make sure to use /ExitAfter:1 so it releases the wait when done. Btw that first "" after the /WAIT is needed.

Other than providing the preset to double-check if something crucial was removed or disabled, I would suggest to refresh the OS with the same ISO + Updates + Removals and run setup.exe to fix your host, or even better use Host Refresh wizard. If using the manual way, make sure: - not to enable...

So not even possible with active ESU on the Win10 host? In that case I'll block/warn it in the UI when image is a target. Thanks for the info.

Thanks. Released an update, you should be able to remove 'Windows AI Machine Learning' without breaking this now.

Checkpoint is not pre-selected if installed. Most likely was the ISO then. Do correct me if proven otherwise on both accounts. Thanks.

Hi, that doesn't look normal, and they all share that misterious "The network name cannot be found" error. Please repeat it by unloading all mounted images, rebooting and deleting the image edits. Then recopy new edit from the original ISO, load and repeat, but only for 2 cumulative updates...

You can change the Temporary directory in the Menu - Settings of the tool. Prior that unload any mounted images. Best is to reboot and start over from fresh ISO files, this is not a known error, something basic got corrupted. Let me know how it goes after trying the described. Attach...

When all 5 are spent, contact me over email for a reset. Then depends on the stats, cannot have infinite activations. Basically one user on one license should not go through 5 machines that easily. Renewals also reset it, so it's never an issue. Excluding VMs which can mess it up, so please be...

Activation process is the same each time: Menu - Manage License - Licensed Paste the license code to the right Press Activate. Server will keep track of activated machines (encrypted, no private data), restoring existing ones, or use another slot for a different one, included is up to 5...

Hi, tested it now and all good. Looking at the log screenshot on the right, the ERROR: Dinit.session: 273, means your DISM (piece of Windows used for integration) is broken. Try it on another machine to confirm, then fix the first one. You can also deploy a virtual machine with fresh Windows...

Finally the camera arrived. So at first I did see what you saw in the first post, even on full Windows. I then installed Logi Options+ for this particular camera, updated firmware, went to Windows Update and installed Logitech USB driver that was listed there. It's somehow important for Windows...

Thank you, the reason was that IOTEnterpriseS edition actually has EnterpriseS license, "IOT" part is ignored. I could not replicate with other editions. Fix will be in the next update when more changes are collected.

There is currently no known issues on 28000, latest version of NTLite does support it as indicated in the changelog. Feel free to open a new topic if you see any issues.

Google tells me it's November 28th.

Thanks, checking the preset difference, unfortunately no obvious causes. Potentially disabled Windows Update driver updates and integrated Drivers, stretching it. Also bit suspicious is Disable background apps in Windows 11.reg More info once I get the hardware, if replicated, it will be easy...

Since my camera doesn't have Hello Face support, had to order another. Give me a few days to replicate this. Until then if you have a working preset, let me know and I can try to guess which removal it is - or let's wait, I needed this hardware for testing anyway.

OK, testing your preset.

Is Camera allowed in Settings - Privacy? https://learn-attachment.microsoft.com/api/attachments/77587-ca1.png Assuming the same camera supported Hello Face on full Windows.

No, it might be that the new component Feature Configuration is needed for all except 24H2 and 25H2. It is listed for Win11+, didn't know it's needed for 23H2, will lock that as my current testing shows it fails like Windows 10 with it removed.