Valhalla_tech
Member
- Reaction score
- 1
- Location
- NC
Hey gang:
One of the things I've never been able to figure out in a in-depth manner, is creating an AIO solution for installing Windows. Basically, I like have a flash drive with all the viable versions of Windows on it (7,8.1,10, etc.) I've tried to create on using a combination of tools, WinAIO Maker Pro, NT Lite (for slipstreaming updates), and, of course, Rufus. However, I had no luck. I could only get the installation to recognize only one of the versions of Windows, even though all of the versions were saved to the ISO. Could be because I was trying to make it dual architecture, which I don't think is possible, but I'm not sure.
Anyhoo, I got my hands on a, ready made, 64 bit AIO, with the aforementioned Windows versions. When I tested it on a virtual machine, that I used VMWare Workstation to create, it loads the setup with a Windows 10 interface and installed fine. However, I'm on site, ATM, and tried to launch recovery console on a Windows 10 machine, and now it's loading the setup environment with Windows 7 interface, and, of course, won't launch the recovery console, because it's trying to launch the Windows 7 recovery console on a Windows 10 machine, which doesn't work.
I'm wondering, how do I determine what interface the setup launcher uses? Why would the Windows 10 environment load on my VM, but Windows 7 load on a physical machine? And, ideally, what is the best way to create my own AIO, so I can customize it. What are the best and/or easiest tools to use, etc.? Thanks to any and all suggestions, comments, and support, in advance.
Cheers,
Fred Smith
Valhalla Tech
One of the things I've never been able to figure out in a in-depth manner, is creating an AIO solution for installing Windows. Basically, I like have a flash drive with all the viable versions of Windows on it (7,8.1,10, etc.) I've tried to create on using a combination of tools, WinAIO Maker Pro, NT Lite (for slipstreaming updates), and, of course, Rufus. However, I had no luck. I could only get the installation to recognize only one of the versions of Windows, even though all of the versions were saved to the ISO. Could be because I was trying to make it dual architecture, which I don't think is possible, but I'm not sure.
Anyhoo, I got my hands on a, ready made, 64 bit AIO, with the aforementioned Windows versions. When I tested it on a virtual machine, that I used VMWare Workstation to create, it loads the setup with a Windows 10 interface and installed fine. However, I'm on site, ATM, and tried to launch recovery console on a Windows 10 machine, and now it's loading the setup environment with Windows 7 interface, and, of course, won't launch the recovery console, because it's trying to launch the Windows 7 recovery console on a Windows 10 machine, which doesn't work.
I'm wondering, how do I determine what interface the setup launcher uses? Why would the Windows 10 environment load on my VM, but Windows 7 load on a physical machine? And, ideally, what is the best way to create my own AIO, so I can customize it. What are the best and/or easiest tools to use, etc.? Thanks to any and all suggestions, comments, and support, in advance.
Cheers,
Fred Smith
Valhalla Tech