Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country


About click-click

Profile Information

  • OS
    Windows 7 x86

Recent Profile Visitors

2,501 profile views

click-click's Achievements



  1. What I don't understand is how WinNTsetup ended up using the directory where I had the drivers for my Win7 installs. Are you simply searching on inf files and applying them when the combo box is empty?
  2. Latest release updating drivers even though .ini has drivers= for a Win10 install. Similar to previous problem applying default unattended xml file even though not selected. WinNTSetup.log
  3. GUI is out of proportion on Win7. Same problem with W8.1 and W10 LTSB. V5.01
  4. The unattend path was blank on both v4 and v5 runs, but V5 looks like it used the xml according to the message. I did not choose that option in either version and used the same ini.
  5. I did a quick compare between v4.6.5 and 5.0 installing Win11 Pro and noticed v5 has Using user defined unattend.xml: U:\SwApps\Tools4Maint\WinNTSetup\WinNTSetup_v5\\unattend\ whereas on v4.6.5 there is no such msg. Is the Win7-11-Select.xml applied in any way on v5, but not on V4 and will this conflict with my unattend.xml which I normally copy to \Windows\Panther\ and what does this WinNTSetup unattend actually do? Other than that, Win11 installed fine, but I only booted into sysprep and did not go further. I tried Mode: wimboot on V5 and Win11 would not install and died. All my drives are BIOS-MBR and was surprised Win11 did not complain and let me install on my test partition.
  6. Sorry to hear that. Since it's now eol, do you have a suggestion how I might still get these bits and pieces without the whole ADK?
  7. Using those drivers only work on one laptop and not on the other. I already said that. I have used the same drivers you are offering. Where in the world do you get the idea that I'm using VMware Thinapp? I don't use that at all. All the drivers I have tried will work, but not for both laptops. I'm trying to find a way to make it work for both with a Win7 flash VHD. Do you understand what I'm saying?
  8. @JFX The vhd will not boot (07B) from either machine via USB3 unless I add the intended storage driver for that machine along with the generic usb3 drivers. Booting the same VHD from USB2 or the HDD works. I don't understand why the storage driver needs to installed when I boot from USB3. For all other non-USB3 cases, booting works fine without the storage driver being installed and Win7 ends up using its own storage driver. This is frustrating. I have one laptop that has both USB2 and USB3. USB2 is fine without the storage driver and USB3 only works if I add the storage driver. Drivers.txt
  9. @Asifmute Not sure what you are trying to say. Booting with the generic USB3 drivers work, but not on all machines and I'm trying to find out why. Using VHD. Machine 1: Intel(R) 6th Generation Core Processor Family Platform I/O SATA AHCI Controller Machine 2: Intel(R) 7 Series Chipset Family SATA ACHI Controller
  10. The reason why I thought it was the iastor.sys was because I removed the storage driver from the vhd that was booting fine and it also ended up with the same BSOD 7b after showing the colored flag for a while.
  11. You were right. I redid adding the drivers and boot was okay, but on the other laptop, the system started and showed the colored flag for a while and then BSOD 7b. I think it has to do with the ACHI controller driver (iaStor.sys). Each system uses a different one. Looks like I need a generic driver for that too.
  12. Okay, I applied the generic drivers to the working flash, The Boot failed with File: \ucx01000.sys 0xc000035a critical system driver is missing or corrupt. The add Driver Folder had all the files mentioned in the readme. WorkingDrivers.txt WinNTSetup.log AddedDrivers.txt

  • Create New...