click-click

I wanted to test this using en_Win10_1709_multi_dec_x86_dvd_100406359.iso to see what the offset was for the install.wim, but nothing gets listed just specifying install.wim. If I leave the [file] blank, I get the following: [README.TXT] Range=51200-51334 [[BOOT]\1-Boot-NoEmul.img] Range=1064960-1069055 [[BOOT]\2-Boot-NoEmul.img] Range=1069056-1069567 How does one specify the [file] in the iso to get it's range, or is iso2offset only for the ADK? I don't have the ADK downloaded so I can't get a list of any offsets from that.

Thanks.. I'm not sure what to do with the cab files. Will the msi know what to do with them? I could not get the adksetup.exe to work for me. I only selected Application Compatibility Tools and the download would always fail. I finally figured out that I needed the 1607 version (10.1.14393 ) of the adksetup.exe for it to work. Edit: I ran the msi from your link and that was enough for what I needed to do. I used the Compatability Adminstrator from the installed toolkit to unblock the Power Manager setup.exe so I could see if the app still works on W10 and it does.

Can this tool be used to get only the Application Compatibility Toolkit (ACT)) from the ADK? I have a program (Lenovo Power Manager) that I want to install but it is blocked for W10, I understand it can be unblocked with ACT, but I don't really want to install the ADK just to get this component. What would I need to enter using GWT -range

Now that's thinking ahead. I don't have Winbuilder installed and wasn't to keen on doing so. You saved the day with this nifty tool and thanks for the heads-up on v2. Is that the recommended one?

The exe file sizes from this link are much smaller than the ones downloaded using the link on page 1. Are these the same versions compiled differently?

Can someone give me a download link for RunScanner 1.0.0.28? The Paraglider site only has 1.0.0.25 available for download, I believe he updated RunSanner for W10, but I can't find a download for it.

Is VHDX also supported by WinNTSetup when installing W8.1 and W10 to a vhd and will WinNTSetup create it for me? The reason I ask is that VHDX supports trim and VHD doesn't. Using a VHDX would allow me to use a USB3 attached SSD for installing W8.1 or W10.

I'm not sure it confirms anything now. I just did a new clean install as before using the tweak via WinNTSetup and this is what I am seeing below. The only difference I can make out is that this time I was connnected to the network after the final install reboot. Drivers for my Ethernet are already included and I happened to be on my docking station which has an Ethernet connection. I checked the registry and it agrees with the tweak. The interesting thing is that the event viewer shows a lot of warnings: Access to drivers on Windows Update was blocked by policy, but somehow WU ended up offering the drivers anyway.

okay, letting WinNTSetup run the SearchOrderConfig tweak is working now for me too. When applied with WinNTSetup, the tweak tends to influence WU differently than at the point when I applied it. Before, I set the tweak via a remote registry edit after WinNTSetup had finished installing the image. Seems like either way should have worked. I don't know why my test did not work since I checked the registry after booting to make sure my remote edit was there.

okay, I will try SearchOrderConfig tweak via WinNTSetup starting from the beginning and see what happens.

Thanks, I tried that, but when I select check for updates, I get about 8-10 driver offers for my Thinkpad. So far, breaking the driver check with -wuuhext.dl is the only thing that worked for me, but I'm not sure what ramifications doing this on my system will have. Setting SearchOrderConfig doesn't seem to be enough.

I would like to add a reg update that can only be updated with elevated privileges. I was able to update it running as TrustedInstaller, but I'm not sure if something less will also work. The key is as follows: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UpdateHandlers\Driver] "DLL"="-wuuhext.dll" I'm trying to keep WU for W10 from offering Driver Updates. Is WinNTSetup able to update these kind of protected keys during setup?

When adding more than one driver, do I put all the driver package files in one directory?

I'm back in business now. I don't know what happened the last time when my MBR was overwritten. Maybe I unknowingly used the old version. This time the yellow ball stayed yellow. Sorry for the confusion BTW, what is the ini setting for /nobootsect ? WinNTSetup.log

Sorry, old version from a disk that I restored. I will redo an install ans send the correct info.

From the drop-down in the GUI (do not update boot code). Did not know there was an ini entry or cmdline parm for that. I must have missed the discussion about it. What is the ini entry supposed to be? I see BootSect=2 after I updated to the newer .ini WinNTSetup.log

During WinNTSetup. It happens at the very end after the updating boot code message. The yellow ball then turns green. I can't find a log file. Is it supposed to be on the drive where the system is installed? If you have a binary compare app, I can send you the before and after versions of the MBR I'm not sure if the mbr exe uses the same amount of code for the MBR like Bootit Bare Metal.

Just tried the new version. MBR0 is still being updated during setup and partially overwriting my 3rd party bootManager

Oh, Sorry, I missed seeing the [WinNT6\TWEAKS] section. Did you add a new option in this update to not update the mbr? Yellow doesn't necessarily mean booting a system will fail as indicated in the information balloon.

Hi JFX, XP install is not a problem, because I am still able to reactivate Bootit with the BBM USB Install ISO. On the other installs, the BBM USB install ISO cannot reactivate and requires you to do a new install because too much of the code in the MBR was overwritten. I would like to avoid restoring the MBR after using WinNTSetup and it would be nice if updating the MBR could be avoided when possible. I still don't understand why none of my reg tweak selections did not appear in the GUI. Was I just missing the RegTweaks= entry? Thanks..

I have bee having some minor issues with WinNTSetup lately. My .ini file that I have been using for ages is now missing all the tweak check-marks that I had selected a while back. I'm wondering why WinNTSetup is not setting these selections. I created a new ini with ctrl+s and noticed the following entries that have been added which I do not have in my old ini file: RegTweaks= [WinNT6\READY] OEM=\sources\$OEM$ Reboot=0 BCD=1 BootSect=2 Win7USBBoot=0 AddOtherOS=0 I seemed to have missed any mention as to what these entries do. After adding them, my check-marks were back. Another problem I am having, is that my bootmanager (Bootit Bare Metal from Terabyte Unlimited), is overwritten when I do a new install with WinNTSetup. I believe BBM sits in the MBR on HD0. WinNTSetp shows the MBR as yellow, which should be ok, but the MBR gets overwritten anyway even though I specify not to update the boot code. Once this happens, my bootmanager is gone. Can you think of a way to avoid this? I'm not sure if this has something to do with the BIOS on my new laptop. On my old Thinkpad T500 I never had to reinstall the bootmanager. Sometimes I had to reactivate it when I reinstalled XP, but that was about it.

Ooops .... deleted

Now that was easy. Thanks - I has forgotten about that. I did complicate matters because I used option 2 instead of option 3 and the Win7PE ended up with a blus screen. After the fact, I found a note to myself: "Use option three in Make_PE3 for rebuild (_Make_PE3.cmd). Do not copy files from current windows7 since this will break IE8 if IE9 or greater is installed on the current Win7." I had a backup of my MakePE3 aetup, so I restored that and only added the usb3 drivers without copying any windows files from my current system (Option3) and I was back in business. After booting the flash on the new lappy, I could see the flash listed and had access to it.

Rebuild with usb3 support. Thanks for the other links - appreciate it.

Hi, I have a new laptop that only has USB3 ports and my MakePE3 doesn't recognize anything on those ports. I can boot, the MakePE iso from the flash drive. but after the system is up there is no flash drive listed. I need to add usb3 drivers to MakePe, but it's been so long since I built a new one, I'm not sure anymore how to add this driver. Before I start researching again, could someone that knows please give me some quick instructions on how to best acomplish this?