KB2603229: is this update merely a reg tweak? Or does it replace any files? If it is just a reg tweak, I will integrate it into my image rather than apply the update post-install.
It wont work because uses a EXE to do the updating of the registry entry, waik will not be able to mount the hive and run the exe for offline purposes. The best thing to do is use something like regshot to track the changes and mount the specific hive then apply the changes manually If you do that there will be no need for the hotfix at all
I'd be happy to test this, but I can't reliably reproduce the problem. It just happened randomly (and only a couple times). As a side-note, I was using a beta Catalyst driver for a week or so, but replaced it with the official release yesterday. That driver was causing other issues so it may have been the culprit for me. But if you have a test-version of your batch file, you could send it to me and I'll try to help narrow things down.
Yes, RegShot was what I was thinking, too. The way I build images, it is in two stages (but happens in 'one go'): first, the integration of updates and some other files in the install.wim; second, an 'overlay' folder structure that also includes reg tweaks, but where I can also add in things like apps, wallpapers, themes, etc. So I have a collection of reg tweaks there that get applied at First Logon stage (right after fresh install but before first desktop view). This makes things very easy and customizable. The reason we do it this way is because the overlay part allows you to change out and update customizations and apps easily, whereas with the install.wim part it has to be integrated, which involves mounting, and is thus more set in stone. So after updating install.wim, applying the overlay, then the bootable iso is built. EDIT: converting into reg tweak won't work for me, it shows many, many entries and it is not clear to me if it can even be done this way. But since SoLoR says it won't error out upon integration, I wonder if it can be intergrated to offline image without a problem.
@Trinket, you also know why it probably wont work is because RegisteredOwner/Organization is stuff that is added by your autounattend.xml or depending upon the options you enter during install...this is why it needs to be run after oobe
I timed the installation of .NET 4.5 on my test machines without any hotfixes: 2min 50 sec with hotfixes: 8min 30 sec Something is definitely wrong here...
Keep in mind SP2 is likely to be quite underwhelming. Microsoft aren't going to be releasing something substantial for Windows 7 around the time of the Windows 8 release, and saying that in itself gives you an idea of the timeframe. Although running a beta of SP2 may be interesting, it may not represent an advantage over running all the latest LDR branch updates. In actual fact, it will probably be disadvantageous as any updates compiled after the beta won't be included in it. Unfortunately leaks are usually at least a month or two behind, likewise with official beta releases, and it may be a couple of months before the next one. This leads the intention of having an updated system with the beta SP2 rather un-updated since you are missing the post-compile updates.
So what does this mean... No hotfixes custom batch file (does this and that): 0:00:38.42 .NET 4.5 installation: 0:03:13.73 office 2010 installation: 0:09:32.44 purandefrag (c: 0:02:27.60 (you may consider this not a good way to benchmark, but everything is installed unattended the exact same way with or without hotfixes to a clean partition) GDR+LDR (integrated to install.wim via modified burfadel script, essentially the same thing) custom batch file (does this and that): 0:01:12.13 .NET 4.5 installation: 0:07:50.78 office 2010 installation: 0:09:36.04 purandefrag (c: 0:02:45.42 (you may consider this not a good way to benchmark, but everything is installed unattended the exact same way with or without hotfixes to a clean partition) Update: OK I believe the reason why it's slow is because the system seem to do some stuff in background, perhaps of relating to hotfixes, I'm not sure, so prior to running my timers, i let the system idle for a while. then everything became a lot quicker
Thanks for taking the time to track the issue down. It's probably .NET doing its initial update. More info: hxxp://blogs.msdn.com/b/davidnotario/archive/2005/04/27/412838.aspx Process Explorer is a great tool to see if it is mscorsvw.exe (or something else). hxxp://technet.microsoft.com/en-us/sysinternals/bb896653
"%windir%\Microsoft.NET\Framework64\v2.0.50727\ngen.exe" executequeueditems /nologo /silent fixed. will let this run first before other stuff. now to find out if we can precompile these into install.wim. any idea? and eh, is it actually possible to integrate .net 4.5 into win7?
KB2544514(Update 4.0.2 for Microsoft .NET Framework 4 – Runtime Update) replaces KB2478063. hxxp://support.microsoft.com/kb/2544514