Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

1 Neutral

About click-click

Profile Information

  • Country

Recent Profile Visitors

850 profile views
  1. WinNTSetup v3.8.7.4

    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.
  2. WinNTSetup v3.8.7.4

    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.
  3. WinNTSetup v3.8.7.4

    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.
  4. WinNTSetup v3.8.7.4

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

    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.
  6. WinNTSetup v3.8.7.4

    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?
  7. WinNTSetup v3.8.7.4

    When adding more than one driver, do I put all the driver package files in one directory?
  8. WinNTSetup v3.8.7.4

    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
  9. WinNTSetup v3.8.7.4

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

    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
  11. WinNTSetup v3.8.7.4

    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.
  12. WinNTSetup v3.8.7.4

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

    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.
  14. WinNTSetup v3.8.7.4

    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..
  15. WinNTSetup v3.8.7.4

    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.