Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by clarkg888

  1. 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.
  2. OK, I finally got the time to try this. I used your autounattend.xml with the image name changed from "Windows 7 Revolution" to "Windows 7 Ultimate" and the Product key section removed: <ProductKey> <WillShowUI>OnError</WillShowUI> <Key>XXXX-XXXX-XXXX-XXXX-XXXX</Key> </ProductKey> I used the US English iso X17-59465.iso Windows 7 Ultimate SP1. I think you must use the French one. I installed in a VMWare VM with 1.5GB RAM and two formatted 30GB drives C: and D: The Users and ProgramData folders ended up on D: as expected. I don't know what is going wrong for you. Clark.
  3. Hello ZERO_XP I add several .reg files to tweaks in my Windows 7 SP1 integration, using WinToolkit and it is working fine for me. Was this working for you before? Perhaps you could share the .reg file? Clark.
  4. Sorry I haven't replied earlier. I'm going to try using your Autounattend.xml sometime after Christmas and see what happens. Clark.
  5. Yes, assuming you are burning the contents of C:\MYDVD to DVD or creating the ISO for install in the VM from the contents. But the OOBE.CMD isn't required to get the Users folder on the D: drive. Maybe try putting your Autounattend.xml on the root of a virgin untouched Windows 7 SP1 Ultimate DVD or ISO ? Clark. Edit: yes, your result with OOBE1.log is expected, since you don't have the OEMACT.CMD file. I'm assuming you are getting no OOBE2.log, so the second pass isn't running.
  6. I don't think that <cpi:.. line matters. I got that line after editing with Windows System Image Manger (SIM). According to this post , you can delete that line. Does the install proceed ok, but just doesn't put \Users on the D: drive? Or do you get some error message? Are you installing in a VM? I've never used audit mode for this. I just add the AutoUnattend.xml to the root of the ISO created with WinToolKit using an ISO editing tool. I use UltraISO. Also, if you are adding a OOBE.CMD script to your ISO in path "\sources\$oem$\$$\Setup\scripts", the script gets run TWICE when you have the FolderLocations specified in the AutoUnattend.xml. It runs once before the \Users folder is moved, then the system reboots and it runs again with the \Users in the new location. I've attached my OOBE.CMD for your reference. It creates a log file on the first run, so it can detect whether this is the first or second run. It runs an OEM activation script on the first pass. On the second pass, it fixes the junctions "Documents and Settings" and ProgramData on the boot (C:) drive so they point to the new location on the D: drive. And it creates a junction "Users" on the C: drive to point to the D: drive so brain-dead software that assumes Users is on the C: drive goes to the right location. This is just a refinement once you've got \Users being created correctly on your D: drive when you install. Clark. OOBE.CMD
  7. Hi Alpha_95: I've done this successfully. I test with VMWare Player with a pair of 30GB.hard disks configured. I have both hard drives formatted NTFS before install. I've attached my Autounattend.xml file for reference. The last time I tested this was about 6 months ago with the prior version of WinToolkit Hope this helps, Clark. Autounattend.xml
  8. 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.
  9. 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.
  10. 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 ).
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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, but the Runonce installation worked fine worked fine with Clark.
  16. 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.
  17. 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.
  18. Still has on the distribution web site: http://www.adobe.com/ca/products/flashplayer/distribution3.html and from http://get.adobe.com/ca/flashplayer/just now.
  19. 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.
  20. 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).
  21. I got that error when I tried to create the ISO when the ISO was still opened by VMWare Player in the VM I still had running. Another possible source of this error. Clark.
  22. Hi pennsylvaniaron, Regarding the difference between WHDownloader and WUD. WHDownloader downloads all Windows updates *and* hotfixes not supplied by Windows Update. WUD just does Windows Updates. Also, if you download everything in the WHDownloader list, you definitely do *NOT* want to integrate all of them. For example, for Windows 7, you can download updates for IE9 and IE10 if you choose to update to those instead of IE11. But if you're updating to IE11, you don't want to integrate the IE9 and IE10 stuff. Also, you can't integrate the stuff in the Additional\_NotAllowedOffline folder. Clark.
  23. I agree with JGToy. Downloading test builds directly from the Latest builds link works fine. The links on the page go directly to the file. For example: WinToolkit_1.5.3.2_Portable.7z 3.42MB Wednesday 29th October 2014 3:36pm However, when the test builds get removed from the page, a link to the official download page at http://www.wincert.net/forum/files/file/5-win-toolkit/ is put there instead. When we click on the Download button on that page, I go to a url like this: http://www.wincert.net/forum/files/go/975c2b37e45c810580a7252bba3fd8ce/win-toolkit The portable Download button on that page links to http://www.wincert.net/forum/files/get/975c2b37e45c810580a7252bba3fd8ce/2243-WinToolkit_1.5.2.16_Portable.7z This is where I get the corrupt download. I always get a corrupt download on my main Windows XP machine. I just tried on a Windows 7 VM on that same machine and it downloaded correctly! There is some weird interaction between wincert and my machine. Clark.
  24. That's the thing: this is only affecting some of us. I've repeatedly downloaded the file to my computer and got the corrupt file with size 3,587,833 bytes. When I download on my work computer at work, I get the valid file with size 3,587,798 bytes: 35 extra bytes. I'm not seeing this issue with any other site. I tried turning off my AV (NOD32 version 8) and connecting through a VPN tunnel: made no difference. I'm going to try another computer at home and report back. We saw the same thing with WinToolkit_1.5.2.13_Portable.7z. I compared the bad download I got with the version that another member made available that was known good. My bad version had 35 extra bytes: 10 bytes inserted at location 35c000h, 10 bytes at 35d000h and 15 bytes tacked on the end. Very strange...
  • Create New...