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


Everything posted by click-click

  1. With the Rufus setup with NTFS, booting UEFI flash with 64-bit OS on a 64-bit machine now works via F12 boot menu, but booting is ignored on my BIOS machine via F12 Boot menu. I have to boot it directly from my Bootit Bare Metal boot menu. Not sure why though.
  2. I redid a flash with Rufus with NTFS support and copied everything over. On the first try, the boot started, but then complained about bootx64.efi missing, so I copied that over into \EFI\boot and got further. Now I'm stuck with the following error. Can't find winload.efi I think the new Lenovo E15 is a 64-bit machine which is why I think the HW was looking for bootx64.efi. Could my problem be that booting a 32-bit Win 10 with UEFI is not supported on that machine? If this is the case, will installing a 64-bit in the vhd be enough?
  3. Same problem and still ignoring. Boots ok on the non-uefi laptop. Does it make any difference if secure boot is turned off?
  4. I did the shrink and copied the files and looked at the BCD in \EFI\Microsoft\Boot\ and the disk and partition entries are blank again. Should I redo them like I originally did above?
  5. One partiton as below. What do you suggest? Make a new flash as exfat or Fat32
  6. A friend of mine asked me to do the setup of a new Lenovo E15 Gen 3 Laptop and I wanted to do a backup of the original system before doing anything. I have a bootable usb recovery flash drive where I installed W10 10 LTSB 32-bit in a vhd with WinNTSetup and I don't have any problems booting it from My lenovo L460 where I have legacy CSM enabled. The E15 is pure UEFI and when I select my flash from the F12-boot menu, it ignores the Ultra Flash and won't even start booting it. I tried turning off secure boot, but that did not help. The partition on the flash is set active. Since I'm not familiar with UEFI, I need some pointers on what needs to be done to make the flash bootable on the E15. Thanks for any help. I edited the G:\EFI\Microsoft\Boot\BCD, but that did not help either ?
  7. I did manage to manually update HKLM\SYSTEM\MountedDevices with the correct value for c: and the system came up fine. Thanks for mentioning leaving out the installation source. Great stuff. I either forgot or didn't realize you could use WinNTSetup without specifying an image. Guten Rutch und ein frohes neues Jahr ....
  8. I have a new system that I installed and tested on Q: I did a backup of the system and restored it to T: I edited the BCD from the restored image to boot from the T: partition, but the system boot isn't running like it should. It takes forever to get to the desktop and that shows up with a black background. I still need to make additional changes in order for the system start correctly. Another thing that I tried was to capture the Q: partition and then apply with dism, but that doesn't create a BCD and won't boot. I then tried applying the capture with WinNTSetup and the system booted fine from the new partition. I need to know what other commands WinNTSetup uses to make this work so that I can apply the changes to my restored image without making and applying a capture. I would appreciate some pointers. I think it may have to do with the system having invalid mount points. No sure though.
  9. FYI, Mediafire list is missing 5.1.2, although I did find it on the Mega list.
  10. 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?
  11. 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
  12. GUI is out of proportion on Win7. Same problem with W8.1 and W10 LTSB. V5.01
  13. 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.
  14. 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.
  15. 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?
  16. 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?
  17. @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
  18. @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
  19. 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.
  20. 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.
  21. 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
  22. I already have those drivers. I will try again and see what happens. uaspstor.cat 19578 2020-06-16 uaspstor.inf 15046 2012-07-26 uaspstor.sys 101832 2012-07-26 ucx01000.sys 216520 2018-05-02 usbd8 .sys 26568 2013-06-29 usbhub3 .sys 452040 2014-07-24 USBXHCI .cat 10374 2021-01-08 USBXHCI .inf 103144 2018-05-01 usbxhci .sys 342472 2017-02-13

  • Create New...