Hellbovine
Well-Known Member
- Messages
- 1,201
- Reaction score
- 748
1) In this thread, the guide states in the beginning steps of 4C to delete old partitions. Are you skipping that step? The thing to pay attention to there is to make sure if you have any additional drives installed that you don't delete the wrong partition. For example, I have a C: drive SSD and another SSD as D: drive, both attached internally. I use C: drive for Windows and software, while I use my D: drive to store backup files, NTLite projects, etcetera. At the Windows Setup screen, I have to always make sure to delete only the 3 partitions that are Windows, without touching the 2nd drive.
2) Be careful with Rufus, it can add its own unattend file that can replace/interfere with a custom one. Rufus isn't needed at all to do anything in my guides or even in the general Windows install process, and more tools used in conjunction with NTLite or guides tends to result in problems due to issues like these that people aren't aware of. More tools also introduce more bugs and opportunity for user error. This guide (link) is how I prepare a Windows image.
3) Virtual machines complicate everything, so always try to install things the real way as a troubleshooting method if it doesn't work in a VM. That software has a number of bugs, as well as quirks that aren't obvious, such as the fact that these types of software can also install their own tweaks without informing the user, and we've had threads here that were resolved only after we discovered it was the VM software intentionally overriding things and causing problems. There's also a lot of general issues with Windows system requirements not being met in misconfigured VM installs.
4) As for trying to use a single drive to have multiple partitions and operating systems, I don't really know the optimal way to handle scenarios like that, because in my view it will always be a suboptimal approach, compared to alternatives that are faster and easier, so I avoid complications like that entirely. For example, installing a second physical drive, so that it's two pieces of hardware will be infinitely easier to manage. That concept is why I have two drives, because then I can keep everything volatile like Windows on C: drive, and all my tools and files on D: drive.
2) Be careful with Rufus, it can add its own unattend file that can replace/interfere with a custom one. Rufus isn't needed at all to do anything in my guides or even in the general Windows install process, and more tools used in conjunction with NTLite or guides tends to result in problems due to issues like these that people aren't aware of. More tools also introduce more bugs and opportunity for user error. This guide (link) is how I prepare a Windows image.
3) Virtual machines complicate everything, so always try to install things the real way as a troubleshooting method if it doesn't work in a VM. That software has a number of bugs, as well as quirks that aren't obvious, such as the fact that these types of software can also install their own tweaks without informing the user, and we've had threads here that were resolved only after we discovered it was the VM software intentionally overriding things and causing problems. There's also a lot of general issues with Windows system requirements not being met in misconfigured VM installs.
4) As for trying to use a single drive to have multiple partitions and operating systems, I don't really know the optimal way to handle scenarios like that, because in my view it will always be a suboptimal approach, compared to alternatives that are faster and easier, so I avoid complications like that entirely. For example, installing a second physical drive, so that it's two pieces of hardware will be infinitely easier to manage. That concept is why I have two drives, because then I can keep everything volatile like Windows on C: drive, and all my tools and files on D: drive.
Last edited:
