Recent content by XYZ

Again, appreciate info. but from multiple test's, plus a few personal mod's, it was the only one I could get to work reliably, for everything I was trying to do, across multiple Windows edition's - most thing's worked in usual way, but some thing's just ended up hanging during install - This way...

For reference - Problem was, some install/config part always hung while installing/config'ing - Never happened with OOBE/OEM/George King's method

Again, really appreciate detailed info. - Think the easiest option's I mentioned are the way to go, but it is nice to know these thing's. On a different topic, when trying to install software and other thing's in NTLite'd ISO, I could never get it to work properly (I tried loads of different...

Thanks for detailed info garlin. Appreciate the help. Given me a few idea's. This bit specifically stuck out as something I need to solve... I know it often reboots once or more times. The different hardware isn't a problem as Windows will often just install the extra driver's needed. It's...

Suppose you only have one computer, but multiple external disk's. What would be the best/easiest way to install a newly NTLite'd Win ISO to a separate drive/disk, without rebooting the one computer (ie. while the one computer is running) ?

Can you make it so that no scroll takes place

The crash is indeed a bug, if caused by buffer overflow, but my original request for NTLite to handle up to 32767 chars still stands. The registry hack will only work on Windows 10, but the method I suggested (ie. prefixing path with "\\? \" and using Unicode versions of Win32 API calls) works...

Legacy apps can support long paths up to 32767 chars if they prefx path with "\\? \" and use Unicode versions of Win32 API calls, which is easy to do. Each component in the path can only be 255 chars, but total length can be 32767 chars. The specific issue I had at the time was on the final...

As per title - Can this be increased to theoretical max char limit ?

For informational purposes, If using the Ventoy tool to boot the Win Setup ISO, you can't use the method laid out in this post to perform the tasks directly from the install media, since when the Win Setup reboots, the ISO is no longer mounted, the step to find the DRIVE that the ESD/WIM/SWM is...

Lets agree to dis-agree, because we do - They are different. It's irrelevant though, as the software is not blocking access to anything apart from pausing it from launching wermgr.exe. When you allow it (haven't tried denying it), it will eventually complete the integration. The point is - Why...

Because this module is an anti-executable, not an AV, so it alerts when it detects a process (in this case DismHost.exe, which was launched by NTLite.exe during processing) starting another process (in this case wermgr.exe). So, it's just informing me that DismHost.exe had some error during...

Don't run an AV

It does seem to end up integrating/completing successfully though, if you leave it long enough. Not sure there's anything you can do though. I wouldn't have known it happened if it wasn't for the fact I run an anti-executable. Below is the error and parameters:

Thanks for detailed reply garlin. 1. Changing the .reg file to set it to Bypass still didn't work (also tried Unrestricted as that's PS 6 default ploicy), but I still got the Execution Policy Change prompt when manually running the imported .ps1 in VM. 2. I agree it's sloppy, but explorer.exe...