bphlpt

And you're giving advice to someone from two and a half years ago via some kind of time machine? LOL Cheers and Regards

Since you say this DisableLangBar.cmd runs correctly as you show it when run from the command line, then leave it exactly like it is and run it with WPI. HKCU exists when WPI runs so it should work just fine. But you can try any other method you like. If you find one that works for you, then please post it so others will know a method you have verified that works. Cheers and Regards

The reason I asked is that this will NOT work during the OS install if it is run too early, since "Current User" - (HKCU) - will not exist at that point as Kel pointed out. So it will not work in Autounattend.xml for the same reason. But I might have misunderstood you. It should work if you run the DisableLangBar.cmd AFTER first log on, using WPI for example. Of course you'll have to run this for each user you want it to apply to. Cheers and Regards

When do you try to run the DisableLangBar.cmd that it does not work? At install, on a live system, anytime, or ...? Cheers and Regards

I really like that none of the tab's names are hidden in the picture above no matter what tab you are on. That arrangement really helps keep me from losing things or forgetting about a tab. When you get around to updating the help files, I would suggest as one of the first pages an outline of all the steps involved in making a build in a logical suggested order. Actually probably two outlines. One for the very basic typical minimum steps and another for an advanced full blown mod and build. In both cases the outline steps could then link to pages with detailed information about how to do that step. Those pages could also have basic and advanced versions. Kind of like the difference between Nero Express and Nero Burning ROM. Yes I know that the beauty of W7T is that you can pretty much do things in the order you want and leave out many of the steps if you want as well. But the wealth of choices and potential steps can overwhelm a new user. They see the tool and say "What do I do first?" Then if a checklist could pop up when they're ready to build, which they can optionally hide once they're comfortable with the process, that could give them a sense of reassurance and a chance to say "Crap, I forgot to do ...!" Just a suggestion. Cheers and Regards

In the meantime try this - http://www.wincert.net/forum/index.php?/topic/9217-proyecto-windows-7-sp1-actualizado/ - It's in Spanish, but Google translate does a decent job. Cheers and Regards

Hey Legolash2o, Have you had a chance to try the new Win8 versions of the tools such as DISM on Win7? I saw a write up about some of the new features here - http://www.msfn.org/...025#entry991025. An especially intriguing new feature to me is the /Remove Parameter in the /Disable-Feature command. If you now run DISM.exe /Online /Disable-Feature /Featurename:SimpleTCP /Remove the SimpleTCP feature is disabled and the files associated with the SimpleTCP Feature are removed. If you run /Get-Features again you see this: Payload Removed = DLLs removed from WinSxS. if you now want to enable the features, the "Turn Windows Features on or off" asks to download the missing files. So this is the safe way to disable features and getting more free HDD space.

This pulls up a 404 page. Not written yet? Cheers and Regards

It's only partially MS's fault. Much of the problem is other software that wants to use a particular .NET feature. If the software checked whether the actual feature was available then many of these problems would be solved. Instead, many apps take the easy way out and just check whether a particular version of .NET is installed that they know has the feature they want to use. It doesn't matter that a later version of .NET also has the feature they could use. They don't check for that because those later versions came out after their software was released. So it's the fault of lazy software writers, some at MS, but mostly everywhere else. Cheers and Regards

No they are still not cumulative. You could conceivably end up needing 1.1, 2.0, 3.0, 3.5, 4.0, and 4.5, and all of the updates to all of them. It all depends on the software you are using. Cheers and Regards

If you knew which of the Driver Packs has some of the files that are the problems, you might can download them here - http://reboot.pro/forum/88/ - you have to be a member, but then it's a direct download. Cheers and Regards

It is ALWAYS STRONGLY suggested to temporarily disable ALL antivirus and antimalware apps of any kind when you are running any builder type app such as W7T. Unplug from the internet while you are "vulnerable" if you are concerned. Use apps from trusted sources and run full system scans on a regular basis and you shouldn't have anything to worry about. Cheers and Regards

Then you were absolutely correct, of course, Kel. Like I said, I hadn't had a chance to check it out. Thanks for keeping on top of things for all of our benefit and safety, not to mention the board's integrity. Cheers and Regards

Kel, I didn't check it out, I'm not a gamer, but if it was this game - http://www.download-free-games.com/freeware_games/chicken_invaders.htm - then I think it was freeware. I know there is free and then there is free, but... Cheers and Regards

As the DISM tools for Win8 get more stable, they should be a godsend for removals, assuming they will be able to be used on Win7, which they should be. See here - http://www.msfn.org/board/topic/153742-dism-improvements-in-windows-8/page__pid__991025#entry991025 Cheers and Regards

I'm don't understand what you want. Can you give an example? Cheers and Regards

So the OP is correct? The tweak doesn't work? Or do we just misunderstand what it is supposed to do? Cheers and Regards

Actually, it's the same user. LOL

The .Net 1.0 is still required, as far as I know, for CODYQX4's Tablet addon, which I saw laddanator was also playing with. I asked in that thread if it had ever been modified to be able to be integrated using RVMi instead of nLite, but don't think that question's ever been answered. Cheers and Regards

According to this link - http://www.autohotke...topic23413.html, it isn't possible, though you would think it should be. Further looking says this works - Shortcuts Map - http://www.zealsofts....com/shortcuts/ And this one claims to as well for x86 OS - Ethervane ActiveHotkeys - http://www.tranglos.com/activehotkeys/ But I have not tested either of these. If you do, or anyone else knows of one that works, and on which OS, please share. Cheers and Regards

RicaNeaga, if I understand laddanator correctly, he is saying that he only does a Win7 rebuild a few times a year, but he modifies his unattend file very often. Yes, as you say, W7T will make a new build that will operate correctly for him thanks to W7T now including the fix that ricktendo came up with and that you championed. But laddanator doesn't need to do a complete new build, which is required in order to inject the new unattend file into boot.wim index 2. He only wants to change the unattend file. Using the mysetup.cmd he outlined above, along with the addition to winpeshl.ini he described, the unattend file now ONLY has to be placed at the root of the DVD, which is easy to do using a UltraIso type app. He can change his unattend file as often as he likes without having to take the extra time to redo his build each time. It also saves having to duplicate the unattend file in two places. This seems like a reasonable enhancement of the current W7T method, as long as the correct behavior if using USB as an install medium is maintained. If you don't think so, why not? In fact I would suggest that the script be further be modified to always look for the unattend file and if not found simply default to the current no unattend behavior silently with no error. You could even further modify it to also allow the possibility that the unattend file is not even located with the install files at all but is perhaps in a different external location specified by a text file. Then the install medium wouldn't have to be modified at all to use a different unattend file. Just edit the unattend file, wherever it is as long as the text file is pointing to it, and go. Just a thought. Cheers and Regards

Windows 7 Toolkit is a marvelous tool that I highly recommend to everyone, but it does not have that feature, because Windows 7 does not have that feature. But you can get that feature, and you don't need this tool to get it. You want "Classic Shell" - http://classicshell.sourceforge.net/ - a free app that you can install on your running system. It can be configured to act in just that manner. Cheers and Regards

If you want to update both x86 and x64 images, you need both sets of updates. Cheers and Regards

If the difference in noise just began when you updated to Win7, it could also be a power preference setting difference. Cheers and Regards

Because it's not proper forum etiquette to post your links in someone else's thread. In this case though, I know that YumeYao and Rick are good friends and have worked together for a long time. We also know that YumeYao is very busy in his job right now and is unable to update his apps as often as we, and he, would like. Even so, as soon as YumeYao is able to come back, I'm sure Rick will remove his posts. Cheers and Regards