bphlpt

So if any new updates seem to cause a problem, post your concerns in the "bugs" section as a potential bug. To help out, try to determine if it is an issue with one or more particular update vs an interaction between updates by at least trying a build with only that one or more particular update that seems to have a problem, and any prerequisites of course, and another build with whatever updates you usually add. Post a copy of the presets you used and whatever logs are generated, along with details of the OS you were working with and that of your host system. Further tests with older Win Toolkit versions or other update options you think might shed some light on the situation can only help but are up to your time and ability. Then see if anyone else is having similar issues. The more background and details we can provide to Liam, the easier his job will be and the quicker a fix can be found. Cheers and Regards

Apparently w32tm /ntte displays its results taking into account the local time zone, since for me the time displayed for the above command is 12:42:02 PM instead of 6:42:02 PM. Cheers and Regards

I guess, similar to how Win Toolkit checks for any AV running upon launch, it could find the latest version of DISM installed and then offer to DL the latest version the host OS can support if there is a later version available? I don't know if that is possible or not, and that assumes that the latest version is just as capable as the Win7 version when used for building Win7 builds. Cheers and Regards

Thanks for the verification. I'm glad it doesn't seem to be a problem after all. I suppose it was just some kind of glitch. Thanks for following up. It is important that our members can post appropriate links when desired. Cheers and Regards

I think what they are trying to modify is the dates shown like in the images posted by abbodi1406 in this post - http://www.wincert.net/forum/topic/12319-windows-installation-where-i-can-change-the-modification-date/?p=108636, where you are selecting which image to install. I can see the value of this when you begin to do an install if the date shown is the date the install source image was created. In other words, if you created one install source in Dec 2013, and another one in June 2014, it would be helpful if those respective creation dates were shown, rather than the RTM date of Win 7 SP1 of 2010 being shown for both install sources such as is shown in the OP of this thread. The creation date of the modified install source is what really tells you how old the image is you are about to install, not the original RTM date, isn't it? Or did I misunderstand what you meant? Cheers and Regards

Hmmm. Did you try to re-edit this post - http://www.wincert.net/forum/topic/10811-15-mars-2014-updates-packs-gdr-windows-7-sp1/?p=108567 - today and add your link back? Because It is still not there. I'm confused. Could you please send me the link via PM and include a description of exactly how and where you tried to insert it, maybe even include a quoted copy of the post with the link inserted in it. If necessary I will ask among the staff to see if anyone deleted it or is aware of this issue. Our members should be able to post links and I'd like to get this problem resolved. Cheers and Regards

Welcome to WinCert! Cheers and Regards

I would think it should be relatively easy to add something such that particular RunOnce entries are used for x64 vs x86. If your desire was to specialize the RunOnce so that some are used for Ultimate and different ones are used for Professional, for example, then that would probably be an entirely different matter. Cheers and Regards

AFAIK that is totally not true. I'm not aware of any problem that the staff as individuals or the WinCert board as a whole has with any links to MSFN, or to any other board for that matter as long as warez is not involved. To my knowledge, for any link that any member posts to be removed requires manual and deliberate action by a member of the staff, and if that happens they almost always post a reason why it was done. If you like, you are welcome to re-edit your previous post and put the link back. Other boards I can think of that are considered friends and you will sometimes see references to are MSFN, RyanVM, BlackViper, ReBoot.Pro, MDL (carefully), ss64.com, robvanderwoulde.com, stackoverflow.com, microsoft.com, and many others. I think at one time in the past there was a policy which restricted references or reposts of material from other boards, but as the technical community has grown, and some boards have specialized in different technical aspects, I think it has been recognized that no one board can have all the people with the answers to all questions and it is in the best interest of our members to refer folks to the best place they can get the help they need, so that restriction has been relaxed. For the convenience of all I believe that it is usually also quite alright to occasionally post a copy or quote from other sources with the key part of the answer, as long as the other source is properly acknowledged and referenced, including a link to the source. Of course it is preferred that we encourage all the smart folks we can find to become members here so that any problems or questions that come up can be answered directly by the ones that know, but when that is not possible ... Outright blatant plagiarism will not be tolerated and will be removed and the member warned and possibly banned if it continues. Cheers and Regards

@Liam, could you please post a list of the KB's that are moved to RunOnce? TIA Cheers and Reagrds

I was wondering about all the talk about v3 and v4 since the latest version I have seen published was WinToolkit_1.4.40. Cheers and Regards

Liam knows this, and he has said he will work on providing the ability to allow Win Toolkit to be translated in other languages in the next generation version of Win Toolkit: Cheers and Regards

The simple workaround is to use RunOnce. Cheers and Regards

@Liam, wouldn't it be a good idea to have Win Toolkit always force this condition?: Is there ever a case when it is better to NOT have Win Toolkit run as an administrator? I can't think of one. Cheers and Regards

I could be wrong, but I was under the impression that the copy happened after install, but before any users were created, which was why sometimes you got unexpected results or duplicate folders created if you tried to copy anything to a particular user's folder, even the built-in Administtrator. Cheers and Regards.

Folks probably forget that, as I did. Maybe there could be a popup, which could be blocked in options but default is to enable, either after RunOnce has run, or when RunOnce is set up, to ask if it would be OK to send the log? Don't know if that would work, but there's got to be a way to remind/encourage folks to send the logs, is they would be of help to you. Cheers and Regards

I thought that was supposed to be happening automatically to help you in your bug hunts, or did you change that behavior? Cheers and Regards

Congrats! I know many will be very glad you will have more time to spend with us here, selfish b@stards that we are. [ I hope you will try to address the RunOnce issues first, especially on x64, that have seemed to have caused the most problems lately. ] Cheers and Regards

© KEiGHT, while you are correct in general, in this case, assuming installation in a Win7 system, you might be mistaken. Higher number versions of .NET 4.5.x completely replaces all lower number versions of .NET 4.x.x. So unless you plan to install to XP, where .NET 4.0 can function and .NET 4.5.x cannot, or you are aware of some software that works with .NET 4.0 and doesn't work with .NET 4.5.x, then in this case I agree with Cartman586 that .NET 4.0 is not necessary. This behavior is different than it was with .NET 3.5.x and earlier where each main prior version, such as 1.0, 1.1, 2.0, 3.0, and 3.5 was an independent entity, and certain software might depend on one particular version, so you had to install them all. And since installing .NET usually takes awhile, this will also save you some installation time. Cheers and Regqards

Ricktendo would be one to ask for pointers about KUC. Cheers and Regards

Thanks. I know you kept on topic. I like your new avatar. Great match for your user name. Cheers and Regards

I don't think you can change the modification date. As to the number of updates, yes Cartman, if you only want to satisfy Windows Update so you get "No updates Required", then the number of 164 seems about right, (I don't know the exact number). But many people also want to install all of the request only updates as well, even if it does take a lot longer to do so. In that case, the number of updates is much, much greater, in fact 300 seems like a low number. © KEiGHT, besides using Win Toolkit, I think you can also use KUC to evaluate whether you have updates that have been superseded. It can work with both online and offline images. You'll have to read the documentation to see how it works. Cheers and Regards

@Cartman586, Please STOP. Assuming that you have posted all the information you have about your problem, you will just have to wait until Liam has a chance to examine the info, see if he can confirm it, then see if he can do anything about it. Posting "See the video", "!!!!!!!!!!!!!!!", "help", and "Please fix" over and over again will not make things happen any faster. You will just have to wait, ..., quietly. We don't know how long. We'll all just have to wait. If you have any new info that might help identify the problem or the solution then by all means post it. Otherwise, please wait. If anyone else has any info or wants to ask any clarifying questions I'm sure they will post. Otherwise, please wait. Thanks for your cooperation. Cheers and Regards

KB2533552 is the one that cannot be removed. Cheers and Regards

The values in those keys were always correct, the problem is in the values in these keys HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\currentversion\RegisteredOrganization HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\currentversion\RegisteredOwner The hotfix changes the values in the HKLM\SOFTWARE\Wow6432Node\ keys to match that of the HKLM\SOFTWARE\ keys. © KEiGHT, you have that backwards. These are for x86 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\currentversion\RegisteredOrganizationHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\currentversion\RegisteredOwnerThese are for x64 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\currentversion\RegisteredOrganizationHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\currentversion\RegisteredOwner CORRECT!! Cheers and Regards