clarkg888

Well, you could burn a bootable OS to DVD and boot from it to delete the files (assuming you have a DVD drive on your system). Something like Windows PE or a Linux Live. Clark.

Hello ZERO_XP I add several .reg files to tweaks in my Windows 7 SP1 integration, using WinToolkit 1.5.4.7 and it is working fine for me. Was this working for you before? Perhaps you could share the .reg file? Clark.

HI Sweden8, I don't think there is a setting in WinToolkit for this. I ended up adding a FirstLogon.cmd in "\sources\$oem$\$1\TEMP\FirstLogon.cmd" on the completed ISO. Containing: I hope this helps, Clark.

Hi symbios24, I used to run WinToolkit under XP. If you integrate KB2966583, all subsequent update integrations will fail. I had to put it in the Silent Installers section. In your case, the update integration is hanging, not failing so this is probably not the issue. I'm just tossing this out there. Clark.

Well, Fred Langa wrote about trying to burn the Windows 10 .iso in the most recent edition of Windows Secrets (and getting the most hilarious error message ever ).

It is not clear at this point, but I think that after upgrading from 7/8 to 10, you get some kind of product key that allows doing a clean install after that on the same hardware using Win10 install media. clark.

Also, once you've determined the changes for one user using way 1 or 2, you can create a .reg file that sets the appropriate keys in the default user tree: HKEY_USERS\.DEFAULT and add this .reg to your tweaks in WinToolkit. Then those settings will be applied to all new users created on the newly install system.

This was added with KB3035583, so just don't integrate that update. Simple as that. Well, maybe not THAT simple. You probably need to turn off Automatic updates so that it doesn't get automatically installed later, and to hide the update. I don't know how you'd hide an update with WinToolkit, probably could use a .reg file. Clark.

WHDownloader only includes the update and hotfixes that result in the most up-to-date version of each file. That means that if a hotfix's files supersede (are newer than) those in a normal previous security update, the security update isn't downloaded. However, Windows Update logic sometimes still asks for the security update. It most cases, it isn't the full update, just a skeleton (you can tell by the size of the update in windows Update). What I and some others do is: 1. Note which updates Windows Updates wants to install that are not in WHD. 2. Download these manually and put in a WU_Satisfy folder. (updates required to 'satisfy Windows Update'). 3. Re-run Wintoolkit, but integrate the WU_Satisfy folder first.

Hi butos, I also add a custom $OEM$ with a setupcomplete.cmd to my Windows 7 iso after Wintoolkit processing to run the SAD3 driver installer. I haven't tested with the latest 1.5.3.13, but the Runonce installation worked fine worked fine with 1.5.3.11. Clark.

I guess it depends. I've successfully added tweaks for IE11 to the default user using a .reg file added to the Tweaks section in WinToolkit and any users I created on the system got the tweaks. YMMV Clark.

Well, your example code is ading to HKLM, so by definition applies to all users. Ya, just add this as a .reg file in the tweaks. Clark.

Still has 16.0.0.235 on the distribution web site: http://www.adobe.com/ca/products/flashplayer/distribution3.html and from http://get.adobe.com/ca/flashplayer/just now.

Hello, Which iso image are you using to start with? For example, I am using the Win7 SP1 x64 Ultimate iso. The image contains Home Basic, Home Premium, Professional and Ultimate. You have to select all the images you want to integrate. I only use Ultimate, so I just integrate to Ultimate. If I then install from that integrated iso, and picked Professional instead of Ultimate, I will see what your are seeing: no updates were integrated. Check which image you are integrating to. clark.

Hmm, Smartscreen is turned on in my custom Win7 X64 wintoolkit-created install. But I've got a bunch of IE customizations through .reg files I add, but nothing related to Smartscreen (as far as I know).