compstuff

I only use x64 Enterprise English on both my Technet and my clients version My Technet: 2.96 GB (3,182,604,288 bytes) File Name: en_windows_7_enterprise_with_sp1_x64_dvd_u_677651.iso CRC32: CE09FA98 Date Published (UTC): 5/12/2011 2:30:00 PM MD5: 6467C3875955DF4514395F0AFCAAA62A SHA-1: A491F985DCCFB5863F31B728DDDBEDB2FF4DF8D1 My Client Volume License that I downloaded from MS: File: SW_DVD5_SA_Win_Ent_7w_SP1_64BIT_English_MLF_X17-27625.ISO CRC-32: dca3cf57 MD4: 7b9530613f911741a0204f08113b0968 MD5: 8db2fa2c64160f582bd099e86dbe219f SHA-1: 2c9774a1f48570e749e6d33c642fe8f6f7898cb0 ‎Created: Thursday, ‎February ‎24, ‎2011, ‏‎3:15:47 PM

Sorry for the delay I was also away after I wrote that post... e-open is just MS licensing model for enterprise customers... same thing as Volume License https://www.microsoft.com/licensing/servicecenter/default.aspx Here is the screenshot which is from the previous post but the same errors I just got http://clip2net.com/s/1KzEd Clearly their seems to be some difference between my Technet image and the image MS has available for the customer... I am running more tests now and will report back

Wow I'm not sure whats going on with my images... I just used a new download from my clients E-Open and did my 2 step test... IE9 and the HF worked... but when I selected the 336 updates the same red ones from above showed up... I am at a loss to understand why.

I wasn't worried about the red but it clearly shows not integrated on the "CPG" image so I am downloading a new one for the client and will test it tonight also...

Here's my update: Fresh integration's of just IE9 Windows6.1-KB982861-x64.msu and IE9-Windows6.1-KB2647516-x64.msu using my TechNet ENT x64 image 1.4.0.T20 TechNet ie9 OK shows 4 updates http://clip2net.com/s/1KCnA 401.3 TechNet http://clip2net.com/s/1KCra red http://clip2net.com/s/1KCtQ shows 4 updates Fresh integration of just IE9 Windows6.1-KB982861-x64.msu and IE9-Windows6.1-KB2647516-x64.msu using my clients ENT x64 image 401.3 CPG http://clip2net.com/s/1KCcc http://clip2net.com/s/1KCe8 red http://clip2net.com/s/1KCgx shows 3 updates

WAIT :-) I think it is really helpful... remember I had asked for a log to help determine what did and didn't install because I could never easily figure out the failed differences but this has certainly helped.

I edited my above response to RicaNeaga since I think I may have been confusing

EDITED: I have been installing Windows6.1-KB982861-x64.msu and IE9-Windows6.1-KB2647516-x64.msu separately in a single step on a vanilla image and they have not given me any trouble

Those are the same I installed using T20 and a different image and they showed installed... so it will take me sometime to test a few scenarios I took the same image and selected just those 6 updates to install and none of them installed I am still reading the links you provided

I think your checking on me LOL

I used the preset and the same 336 hotfixes but I am using the latest release and a different base image... After the integration it shows 333 integrated and the red errors during installation... http://clip2net.com/s/1KzEd I am going to run another test with my original image but it takes 2hrs for this to integrate using my laptop...

Did I just not notice that before :-)

I used a preset for SoLoR updates and it had 336 updates When it was loading the updates it said 336 of 350... when it started integrating it said 336 http://clip2net.com/s/1Kz7W http://clip2net.com/s/1Kz8j

I added the following additions and my image wouldn't boot... \SoLoR\03-19-12\Additions\KB917607.Windows.Help.(WinHlp32.exe)\Windows6.1-KB917607-x64.msu \_Updates\SoLoR\03-19-12\Additions\KB943790.Windows.File.Management.API.(Fmapi.dll)\Windows6.1-KB943790-x64.msu \_Updates\SoLoR\03-19-12\Additions\KB969168.Microsoft.Agent\Windows6.1-KB969168-x64.msu \_Updates\SoLoR\03-19-12\Additions\KB971033.Windows.Activation.Technologies\Windows6.1-KB971033-x64.msu \_Updates\SoLoR\03-19-12\Additions\KB974405.Windows.Identity.Foundation\Windows6.1-KB974405-x64.msu \_Updates\SoLoR\03-19-12\Additions\KB974405.Windows.Identity.Foundation\Hotfixes\Windows6.1-KB2607496-v3-x64.msu \_Updates\SoLoR\03-19-12\Additions\KB2607070.Windows.Update.Agent\CABsForDISM\x64\KB2607070-WUClient-SelfUpdate-ActiveX.cab \_Updates\SoLoR\03-19-12\Additions\KB2607070.Windows.Update.Agent\CABsForDISM\x64\KB2607070-WUClient-SelfUpdate-Aux-TopLevel.cab \_Updates\SoLoR\03-19-12\Additions\KB2607070.Windows.Update.Agent\CABsForDISM\x64\KB2607070-WUClient-SelfUpdate-Core-TopLevel.cab http://clip2net.com/s/1Jzri The image without them booted fine...

Hi Reaper... I never created an addon but before I tried with this one I was wondering if this was the method you used or if you could provide some insight... thanks http://www.wincert.net/forum/index.php?/topic/5833-guide-creating-addons/

Many of you may already know this but it was new to me so I figured I would post it for others: If you get this error when installing WIN7 to Virtual Box: "Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your windows install disk and restart the computer. 2. Choose your language settings, and then click NEXT 3. Click repair the computer. If you do not have the install disk contact your system administrator or computer manufacturer for assistance. Status: 0xc0000225 Info: An unexpected error has occurred." The cause of this problem is the APIC (Advanced Programmable Interrupt Controller), on which Windows depends. You must enable this feature in the virtual machine settings.

That is exactly what I do... I never "re-Integrate" ...I make new ones and use updated drivers, hotfixes, addons, etc.

Thanks Rick... this should help everyone and the new changes make implementing this much easier.

Rick, I know I have asked many questions about this and we all know it seems to be a source of confusion so I would like to ask again for your insight and we can get this info included in the new version and guide. Based on what you mention above and the way 1.4 downloads the SoLoR updates and creates a LDR Placeholders folder... if I check the LDR option and want to include the LDR branch do I keep this placeholders folder so the integration sees them and forces the LDR branch or do I delete the folder so that they are not integrated? What is the definitive way to integrate the LDR branch? Not intending to double post but I also posted here http://www.wincert.net/forum/index.php?/topic/8875-ldr-placeholder/page__p__83319#entry83319 because I thought it was in this forum and not the WIN 7 forum

That's what I had been doing but it seems to not be what Rick is stating above...

Rick, I know I have asked many questions about this and we all know it seems to be a source of confusion so I would like to ask again for your insight and we can get this info included in the new version and guide. Based on what you mention above and the way 1.4 downloads the SoLoR updates and creates a LDR Placeholders folder... if I check the LDR option and want to include the LDR branch do I keep this placeholders folder so the integration sees them and forces the LDR branch or do I delete the folder so that they are not integrated? What is the definitive way to integrate the LDR branch?

Can't believe I missed the damn forum link because I didn't enlarge the image DUH :-) Forget my #4 because once an updated guide is available and a link to it is provided then the existing pop-ups are fine Not sure what others think regarding the version but this is a pretty significant visual and layout change so I think 1.4 is appropriate

Just got a chance to review and you did sooo much.. here's my take: 1) The overall look is extremely clean and sharp... very nice 2) The groups are an excellent addition and are very helpful to both beginners and advance alike 3) I think you should still keep a link to the forum somewhere 4) Some additional explanatory pop-ups over the icons would be helpful 5) Driver and Update installers are clean and straight forward Overall very nice IMHO... THANK YOU!!!

OK... so now I feel like I'm loosing my damn mind... I downloaded r102 and made 2 test runs with the same methods and drivers as my problem sets and I got zero errors and cannot reproduce the problem.

I ran one test and the error didn't happen but I only integrated one set of drivers not both sets so I need to run more tests to really see whats going on.