Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by yogurt

  1. @x23piracy,


    I have searched high and low for more more information ob this odd behavior. But all i can find is either not reliable or solutions such as the one tried. No real reason as to why or what is the problem.


    I suspect it has something do to with the way the partition tables are setup on the source media (in this case a san disk usb drive.) I would start there.

  2. Thtats great, I had a feeling that post #23 would work.  I have seen this unusual annoying behavior, not only with San Disk but other brands as well. 





    i can confirm it's a must to pull the Sandisk USB 3.0 Extreme while partition choosing, then refresh, put in again, another refresh and its possible to install to the hdd.

    Nasty Workaround but i works. :( I want to fix that! but how?



    Greetz X23

  3. From what I can tell all the drivers in DP_Chipset_wnt6-x64_1212 are all signed. In essence the option to force unsigned drivers will have not effect because all drivers in the pack are signed. If for example you were to try an integrate a driver that was unsigned with the Force unsigned unchecked than DISM would throw out an error and pass over the driver. On the hand, with the Force Unsigned checked, would force DISM to integrate the unsigned driver regardless. Hope this helps in your quest for understanding.


    am using: DP_Chipset_wnt6-x64_1212

    My boot.wim was growen before ~190mb now 201mb so something was integrated.

  4. @x23piracy

    Have you looked at the setup logs? http://technet.microsoft.com/en-us/library/dd744583(v=ws.10).aspx


    1. what size is your install.wim?

    2. what file system is your UFD formated with?

    3. have you tried the solution in post #23?


    The solution you describe speaks for my idea that windows trys to install the bootloader in the sandisk stick mistakenly.

    How can i find that out while setup is running, is there a hidden console or something to debug that?

  5. Drivers that are signed can usually be identified by their driver.cat file.  
    Forcing the integration of unsigned drivers means exactly that. You force the driver to be integrated regardless if it signed or not. However doing so can cause various issues during a windows install. It really depends on several factors.

    Digital Signatures (Windows Drivers): http://msdn.microsoft.com/en-ca/library/windows/hardware/ff543743(v=vs.85).aspx

  6. @Etz


    I was under the impression that WinToolkit RunOnce was executed before setupcomplete.cmd and not Setupcomplete.cmd and WinToolkit_Runonce after?


    Possible, use setupcomplete.cmd


    Here is mine:



    @echo on:: Set Pagefile Size to 1024MB fixed Sizewmic computersystem where name="%computername%" set AutomaticManagedPagefile=Falsewmic pagefileset where name="C:\\pagefile.sys" set InitialSize=1024,MaximumSize=1024:: Disable Hibernationpowercfg -h off:: Set Network Interfaces MTUnetsh interface ipv4 set subinterface "Wireless Network Connection" mtu=1430 store=persistentnetsh interface ipv4 set subinterface "Local Area Connection" mtu=9014 store=persistent:: Delete Sensitive Setup Informationdel /Q /F "%WinDir%\system32\sysprep\unattend.xml"del /Q /F "%WinDir%\panther\unattend.xml":: Disable RacTask To Get Sleep Working on Overclocked Z68 Boardschtasks.exe /change /tn \Microsoft\Windows\RAC\RacTask /disable:: Fix Windows WMI Event ID:10 Errorcscript %WinDir%\Setup\Scripts\WMI-Error-ID10-Fix.vbs:: Reboot Computer to finish%WinDir%\system32\shutdown.exe -r -f -t 0


    It reboots machine, before WinToolkit Installer has started...feel free to customize... ;)

  7. No tweak or app added. this is the default behaviour of my Win 7 SP1 (7601) [Vanilla] installation.


    The only sell extensions I have are those of HashCheck and Open Cmd prompt.



    I'm curious. What did App/Tweak did you add that added the "Opens with" and "Security" sections to the General Tab of the Properties box? Any other useful goodies added?

    Cheers and Regards

  8. what happens if i have a image with allready integrated drivers and now o load the preset with the drivers again, will wintoolkit reintegrate all the drivers again or will it detect that this one is allready integrated?


    My understanding is that DISM will process them but skip over them :)


    Actually i always clear the list with the drivers because i allready integrated them. Whats is the right workflow when using wintoolkit.


    It's really a matter of preference, I prefer to use a fresh untouched source, unless it something minor like adding 1 or 2 drivers. My work-flow something like this.

    1. integrate updates

    2. test

    3. Silent installers and SFX

    4. drivers

    5. tweaks

    6. test (optional)

    7. everything else

  9. Just be sure the option is checked before you start the integration. Also I have also notice driver and add-ons not integrating with DISM when trying to integrate driver packs, add-ons and updates that were downloaded from the net using internet explorer. 


    Right click the driver file in question and look at it's proprieties. Under the General Tab look just below the attributes for the file and click unblock. See screen capture for a visual.


    EDIT: As compstuff mentions in the next post Alternate Stream view is also available for bulk unblocking.


    FYI: NTFS Alternate Streams: What, When, and How To



  • Create New...