Well, did you install it? Before packing everything into a silent installer, after applying all the updates to SoLoR's prepped NET framework pack and installing it, this is the overall build number that Windows sees (as in, what shows up in Programs & Features or any uninstaller). Same thing after I install from my silent installer. I know that inside there are many different file versions, but where to get an overall build number if not this way? Installing without the updates yields 4.0.30319, so... you tell me what to do. I'm finding it hard to determine version number on this thing, even the NET verification tool by Aaron Stebner I used on this to verify doesn't help with that. But if there are experts out there, please don't be shy and post your updated installer here
I still find it a bit ambiguous how to tell what the overall version number is, but it's all I can do. Looks like it's working for you too then
All these mentioned versions show up in the Property table of the MSI's (open them with Orca or InstEd) Code: ProductVersion=4.0.30320 ReqCLRVersion=v4.0.30319 RTM_ProductVersion=4.0.30319 URTVersion=4.0.30319 SharedComponentVersion=4.0.31106.0 etc, etc, ProductVersion is the one to go by
Hi Rick, I hope all is well I have a quick question for you I have been working on a sysprep image and have almost everything working but I have two packages that show Staged not installed do you know what I am doing wrong? Here is how I created the first wim that would be the master wim. 1. Started with the original MS SP1 Refresh ISO 2. Integrated all those listed in the following folders on the repo': Windows.7/Hotfixes/x64/IIS/ Windows.7/Hotfixes/x64/MSMQ/ Windows.7/Hotfixes/x64/NFS/ Hotfixes/x64/Integrate to installation media/ (I did not Integrate KB2521168-x64 I could not figure out how to integrate it) and Windows6.1-KB943790-x64 Windows6.1-KB969168-x64 Windows6.1-KB974405-x64 Windows6.1-KB2488113-x64 Windows6.1-KB982861-x64 (IE 9) 3. Then I install theses online in sysprep in this order and reboot after each one. Windows6.1-KB2533552-x64 Windows6.1-KB982018-v3-x64 Windows6.1-KB2528984-x64 Windows6.1-KB2529073-x64 4. Finalize the SysPrep create WIM and then do another install and boot in to Audit Mode to install Apps, Make Reg changes and Desktop changes. 5. Finalize the SysPrep and create the Final WIM for install At what point do you install the rest of the updates? Is it done to the final install after you have installed form the Finial SysPrep WIM? Thanks, Dean Code: ------------------------------------------------------------------------------------------------- | ---------- | --------------- | ------------------ Package Identity | State | Release Type | Install Time ------------------------------------------------------------------------------------------------- | ---------- | --------------- | ------------------ Microsoft-Windows-Agent-Package-TopLevel~31bf3856ad364e35~amd64~~6.1.7600.16426 | Installed | Update | 5/26/2011 5:57 PM Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 | Installed | Language Pack | 5/26/2011 5:57 PM Microsoft-Windows-Client-Refresh-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 | Installed | Language Pack | 5/26/2011 5:57 PM Microsoft-Windows-CodecPack-Basic-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 | Installed | Feature Pack | 11/21/2010 3:40 AM Microsoft-Windows-Fmapi-Package~31bf3856ad364e35~amd64~~6.1.7651.0 | Installed | Feature Pack | 5/26/2011 5:57 PM Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 | Installed | Foundation | 11/21/2010 3:40 AM Microsoft-Windows-Identity-Foundation-Package-TopLevel~31bf3856ad364e35~amd64~~6.1.7600.16394 | Installed | Update | 5/26/2011 5:57 PM Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 | Superseded | Language Pack | 4/12/2011 8:29 AM Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 | Superseded | Feature Pack | 11/21/2010 3:40 AM Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~8.0.7601.17514 | Superseded | Language Pack | 4/12/2011 8:29 AM Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7601.17514 | Superseded | Feature Pack | 11/21/2010 3:40 AM Microsoft-Windows-InternetExplorer-Package-TopLevel~31bf3856ad364e35~amd64~~9.4.8112.16421 | Installed | Update | 5/26/2011 5:57 PM Microsoft-Windows-LocalPack-AU-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 | Installed | Local Pack | 5/26/2011 5:57 PM Microsoft-Windows-LocalPack-CA-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 | Installed | Local Pack | 5/26/2011 5:57 PM Microsoft-Windows-LocalPack-GB-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 | Installed | Local Pack | 5/26/2011 5:57 PM Microsoft-Windows-LocalPack-US-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 | Installed | Local Pack | 5/26/2011 5:57 PM Microsoft-Windows-LocalPack-ZA-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 | Installed | Local Pack | 5/26/2011 5:57 PM Package_for_KB2159360~31bf3856ad364e35~amd64~~6.1.4.0 | Installed | Hotfix | 5/26/2011 5:57 PM Package_for_KB2428216~31bf3856ad364e35~amd64~~6.1.1.0 | Installed | Hotfix | 5/26/2011 5:57 PM Package_for_KB2462576~31bf3856ad364e35~amd64~~6.1.2.0 | Staged | Hotfix | Package_for_KB2485543~31bf3856ad364e35~amd64~~6.1.1.0 | Staged | Hotfix | Package_for_KB2488113_BF~31bf3856ad364e35~amd64~~6.1.1.0 | Installed | Update | 5/26/2011 5:57 PM Package_for_KB2488113~31bf3856ad364e35~amd64~~6.1.1.0 | Installed | Update | 5/26/2011 5:57 PM Package_for_KB2489256_BF~31bf3856ad364e35~amd64~~6.1.1.1 | Installed | Security Update | 5/26/2011 5:57 PM Package_for_KB2489256~31bf3856ad364e35~amd64~~6.1.1.1 | Installed | Security Update | 5/26/2011 5:57 PM Package_for_KB2495655~31bf3856ad364e35~amd64~~6.1.1.0 | Installed | Hotfix | 5/26/2011 5:57 PM Package_for_KB2519454~31bf3856ad364e35~amd64~~6.1.2.0 | Installed | Hotfix | 5/26/2011 5:57 PM Package_for_KB2520513~31bf3856ad364e35~amd64~~6.1.1.0 | Installed | Hotfix | 5/26/2011 5:57 PM Package_for_KB2522807~31bf3856ad364e35~amd64~~6.1.1.0 | Installed | Hotfix | 5/26/2011 5:57 PM Package_for_KB2528984~31bf3856ad364e35~amd64~~6.1.1.0 | Installed | Hotfix | 5/26/2011 6:30 PM Package_for_KB2529073~31bf3856ad364e35~amd64~~6.1.1.1 | Installed | Update | 5/26/2011 6:32 PM Package_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1 | Installed | Update | 5/26/2011 6:14 PM Package_for_KB2534111~31bf3856ad364e35~amd64~~6.1.1.0 | Installed | Hotfix | 5/26/2011 5:57 PM Package_for_KB976902~31bf3856ad364e35~amd64~~6.1.1.17514 | Installed | Update | 11/21/2010 3:01 AM Package_for_KB982018~31bf3856ad364e35~amd64~~6.1.3.2 | Installed | Update | 5/26/2011 6:27 PM The operation completed successfully.
the latest versions of the supersceded removal tool no longer works with directory paths with spaces in them. used to work just fine... back in v14 irc strangely it does work if you put a single " before the path. which makes me think theres an open " somewhere in the path handling
@dolivas I am assuming you did /get-packages to an offline image not after install. Those two hotfixes may not be completely installed because there may be a "stage" or step that is yet to complete (like the MOF files need to be registered with wbem) but sysprep is kinda like safe mode, not many services are running (try using DISM in sysprep you will see what I mean) So if I were you I would not worry and I dont integrate KB2521168 either
That's the odd part.I dont have spaces in update folder paths. It worked for D:\Resources\Hotfixes\New\x64 but not for D:\Resources\Hotfixes\New\x86 Tried pasting "D:\Resources\Hotfixes\New\x86" - still same error. Tried pasting "D:\Resources\Hotfixes\New\x86 - script exits without a warning.
Yes Rick /get-packages was run on the wim created from sysprep offline. Another quick questions after you finish the sysprep in audit mode can you reboot in to audit mode if you have forgot to do something and create another wim or do you have to start over once the SysPrep is completed using the Generalize? Thanks again for the help, Dean
You would have to capture the generalized image and run that in audit mode again to address further customization. You would not have to start from scratch again, just reinstall the resultant captured image to vhd and do whatever afterwhich you just generalize and capture again.