bphlpt

Jeeze! I guess we always need to ask a new poster with a problem to verify the following before we offer any further advice: 1. Is your source image a CLEAN unmodified one? 2. Are you sure you do not have any spaces anywhere in the path or image/file name? 3. Are you running as an administrator? 4. Do you have enough free space on any drive which Win Toolkit might use for any reason? 5. Is your antivirus turned off and disabled? 6. Which version of Win Toolkit are you using? 7. What exact host OS are you using? 8. Which exact OS is the image you are trying to work on? 9. Have you attached your log file? Did I miss any other important questions? Until those questions are answered by a new poster I see no reason to continue the troubleshooting process. Cheers and Regards

Did you try the suggestion by myselfidem? What exactly did you use for your folder location and content? (Don't use the translator for this part, cut and paste exactly what is there using [ code ] tags so we can see the actual folder names you use) Cheers and Regards

What OS are you using as your host OS to run Win Toolkit? Are you running as an administrator or as a "regular" user? Cheers and Regards

As you can tell from under my avatar, I already did, so what are you waiting for? Cheers and Regards

Maybe everyone else is waiting on you to start the ball rolling with the donations? It's got to start somewhere! Cheers and Regards

See this also for another option - http://www.wincert.net/forum/topic/10081-desktop-over-start-ui-in-windows-8-rtm/#entry89697 Cheers and Regards

Yet another choice is this one - "Windows 7 explorer.exe for Windows 8" discussed here http://www.msfn.org/board/topic/157302-windows-7-explorer-for-windows-8/ - You literally replace the explorer.exe of Win 8 with the one from Win 7. The Metro/Modern screen and apps won't run, and I guess some people won't like that will others will rejoice. To each their own. As far as I know, you can still use Classic Shell on top of this as well. Just another option. Cheers and Regards

The easy way to handle this is to not change the boot sequence in the first place, at least not permanently in the BIOS. Usually, at initial machine start up, there is a Fkey option to access boot options. You can then select your USB/CD/DVD to boot from on a "one time only" basis. Then when the machine reboots, after copying all the files it needs to the new C drive, it will boot to the C drive automatically and continue the installation. You then leave your USB/CD/DVD in place until after the install completes and gets to the desktop. That way any files needed for installing apps etc will be available. Cheers and Regards

Were you running as an administrator? Cheers and Regards

I think you were thinking of this post - http://www.cnn.com/2012/09/03/tech/gaming-gadgets/microsoft-windows-7/index.html?iref=obnetwork Cheers and Regards

Thanks, Rick! Cheers and Regards

I haven't been using this app by Geej, but I'm afraid I agree with ionut_y, even though I would probably also use a portable version of the Adobe Reader as HJSC suggests. If the issue does not occur with the official installer of FOXIT, but it does with the one made by Geej, then that kind of implies that Geej should be able to make his so the problem does not occur as well. Whether it would be worth it to do so is another question. Cheers and Regards

@Simpuhl, Please add or bump your requests in the request area. Cheers and Regards

I'm sure Rick knows better than I, but I think the point is not where the actual updates come from, which I think is directly from MS, but where the database of which updates replace which other update etc comes from and is maintained along with the KUC tool itself. That database and the KUC tool that utilizes it was created by and is maintained by Komm, with help and input by all the folks in the thread I mentioned, among others. This is both good and bad. Good, because you have a lot of people looking at this and crosschecking his results, independently testing on different equipment and circumstances etc. Besides, you know that MU/WU stuffs up now and then, so this will bypass that problem. Also, the request only updates will not be listed on MU/WU. Bad, because there is obviously a lag from when something is released by MS and it is verified and added to the database and/or KUC. I think this is "the reason the newest updates from the last month or so is still showing up in MSU". He is only one guy after all. Another problem is that he could decide to take a break, such as SoLoR has done. That's why it's also good that McRip is doing his thing independently, but he is also only one guy. Leoglash20 is also only one guy. All of these guys need and deserve all the help and support we all can give them if we hope to continue to be able to utilize their services. If not, we'll all be left with only MS to turn to, and you've seen what they've done with Metro/Modern/Nameless Piece of Crap or whatever they call it these days. LOL Sorry, I couldn't help myself, but I didn't mean to start a flame war, so just ignore that last bit. Cheers and Regards EDIT: I Hope that eventually Lego will figure out a way to include the option to utilize KUC directly from Win Toolkit, as an option to McRip's database. I think this request has already been made.

Perfectly acceptable approach. Thank You! I would suggest a slight change in wording to: "This can be changed in the 'Misc' tab of 'Options'", or something like that to make it even easier to find. Cheers and Regards

I think crashfly meant that KUC identifies more updates (357) than Win Toolkit (127), for the reason that crashfly explained, and laddanator's experience bears that out. Komm has explained that he hated enabling an optional feature post-install, such as IIS, only to find out that he had to then spend time downloading the required updates for the option before he could begin using the optional feature he just enabled. So he decided that he would set it up so that he could download and "install" all available updates for his system at the beginning, whether they were actually needed at that time or not.. They wouldn't all actually get installed or take up any extra CPU cycles or system resources unless and until the appropriate optional feature was enabled and installed. Until needed they would just be "pending", just taking up disc space, which was cheap and plentiful, ready to be used if necessary. I guess Komm must have been a Boy Scout and taken the "Be Prepared" motto to heart. I believe that you can select various updates, like for IIS, and not "install" those if you know you will never use that feature. Komm also includes all "Request Only" updates that he has been made aware of as crashfly also mentioned. SoLoR started this practice, and McRip (where Win Toolkit currently gets it's list of updates from) continued it as well, and Komm also continued the practice. Including the Request Only updates for all the various features available for Win7 means that Komm's list of available updates is that much larger than that currently used by Win Toolkit. EDIT: If you want to read the whole story and history, and have a lot of time on your hands, Google "SoLoR McRip Komm", without the quotes ("), and you should find a link to a thread on another forum that has had an extremely active discussion going on for well over 2 years with over 6326 posts in that one thread. burfadell is another active contributor there of Win 7 update scripts and tools. If you go there I'm sure you will see many familiar names. Hopefully this explains the "Why?" you asked, laddanator. Cheers and Regards

Fair enough. I assume then that there is at least some popup box or in-your-face notice as to what location has been selected, just so the user can't claim they didn't know that Win Toolkit was going to use XX: disk for its files? I'm really trying to help you keep from having to post RTFM type answers over and over when folks post here wondering why such-and-such disk was chosen. Cheers and Regards

"Better", maybe, in one particular metric, one that has not been a focus of Win Toolkit to this point. Cheers and Regards

Still, I would appreciate the option of overriding the choice even on the first run. Cheers and Regards

It's fine for Win Toolkit to make the determination of where it thinks is the best place, but please then have a box pop up and tell the user where that place is and give them an option to either approve the selection, override the selection with their own choice, or maybe even cancel the whole thing. Cheers and Regards

I think the July 2012 date is the last date the post was updated, probably adding a language version I would guess, not the date of the ISO releases. The links themselves are official MS links hosted at digitalriver. Lego just copied the links here for his users convenience. As to how the last build you made got a later modified date, I don't know. Probably depends on exactly where you got your sources at that time and what you did to build your ISO, ie did you use a source that already had SP1 integrated, was it a "refreshed" source with KB2534111 already included, or did you do any of the integrating/updating yourself? Also the tool you used at that time could have been a factor. Cheers and Regards

I've got stuff piled up from a move 12 years ago. LOL Cheers and Regards

Patience. Cheers and Regards

Be sure to check out http://www.wincert.n...august-29-2012/ and http://www.wincert.net/forum/topic/9521-dougiefreshs-vista-sp2-update-pack-x86-august-29-2012/ You might want to get in touch with dougiefresh to exchange info and advice. Cheers and Regards

And I think the link for "wdfcoinstaller (Windows Driver Framework)" can be found here - http://msdn.microsof...rdware/br259104 - which I found by following another link on the "Windows Driver Kit 8" page - http://msdn.microsof...e/hh852362.aspx Cheers and Regards