click-click

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?

This happened using the latest version of WinNTSetup (3.8.6.0). On my W7 (Starter) system, I created a VHD via Disk Management. Initialized the disk and selected volume type 'New Simple volume'. I then mounted the volume and started WinNTSetup. Select location of Windows installation files: R:\Win10_1511_2_English_x86\install.wim Select location of the Boot drive: c: (Using current boot drive since VHD not allowed) Select location of the Installation drive: c:\W10_Home.vhd Edition: Windows 10 Home Once started, I got the standard message about changing the boot code. I selected BOOTICE in order to later see the boot info. Everything ran to near completion when I got the mentioned errors which most likely came from W7 since you don't use such a dialog . If I run the same configuration and select 'do not change boot code' I do not get any errors and can install and activate W10. I did notice that even though I selected 'do not change boot code', WinNTSetup shows a msg '"changing boot code" at the end of the setup stage.

I just tried installing W10 to a vhd from an active system and towards the end, I see the following msg: The update operation may be unreliable since the volume could not be locked. Continue anyway? If I select yes, I get Write file failed! Access is denied. I'm not sure if I'm following the correct procedure for installing to a vhd. I've always used an empty partition up to now. Anyone know why I'm getting an error?

Makes sense. All I ever added was the PosReady key to keep the updates coming. I never knew that the windowsembedded key served a similar purpose.

Where did the windowsembedded key come from? I don't see it on a normal XP SP3 Pro install.

Does anyone know how to temporarily change the service startup type for msmpsvc (Microsoft Antimalware Service) via the registry or otherwise? Everything I've tried gets access denied. Microsoft made some changes to the protection scheme for MSE. Running Regedit as TrustedInstaller doesn't work.

I think WinNT has more that enough options in it as is. I don't always update when options get added if I can manage without them. The more you add, the more work it is for the developer and the more complicated it gets to maintain. Bite the bullet and use your three screw drivers.

I can live with WU taking longer searching for updates as long as it does this in a reasonable way. What I can't live with, is the amount of CPU it uses to carry out the task. On a dual core T2300, it uses 50-51% CPU during the whole process which is unacceptable. If the system is fully up-to-date, WU is much quicker and If you are missing any updates, it is slow. Vista has the same problem. Win8.1 is better, but they all suffer the high CPU usage.

It's off and on. Seems to be a website problem. [Error number: 0x8DDD0010]

MU website is broken again after installing MS15-106 for IE. I Uninstalled it and the problem went away. Anyone else? Cumulative Security Update for Internet Explorer 8 for WEPOS and POSReady 2009 (KB3093983) Edit: It's not the update. Tried MU again and it's no longer working.

Do you mean sysprep/capture the drive from a winntsetup install, or do I have install from the CD?

I had to reinstall Vista on one of my partitions (Drive0 P0=XP, P1=Vista and Drive1 P0=W7 P1=W81 P2=W10) and I can't get it to boot as the c drive. Even though mount installation drive as C is set, the system drive keeps ending up being assigned to D. Volumes 0-6 are on Disk0 and volumes 7-10 on Disk1. Below is a list of volumes from setupcomplete.cmd. Not sure if I'm doing something wrong. i don't have this problem with the other systems because they all boot as C. Is there any way to change the Vista boot drive back to C ? Microsoft DiskPart version 6.0.6002Copyright (C) 1999-2007 Microsoft Corporation.On computer: 2082-52G Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- ------- Volume 0 K WinXP_Pro NTFS Partition 20 GB Healthy Volume 1 D Windows Vis NTFS Partition 20 GB Healthy System Volume 2 E SYS_Misc NTFS Partition 20 GB Healthy Volume 3 F Temp NTFS Partition 8 GB Healthy Volume 4 G Make_PE NTFS Partition 4511 MB Healthy Volume 5 H SysInstall NTFS Partition 67 GB Healthy Volume 6 I Lenovo NTFS Partition 10 GB Healthy Volume 7 C Windows 7 NTFS Partition 20 GB Healthy Volume 8 L Windows 8.1 NTFS Partition 20 GB Healthy Volume 9 M Windows 10 NTFS Partition 20 GB Healthy Volume 10 J SysMaint NTFS Partition 215 GB HealthyLeaving DiskPart...