Latest hotfixes causing hard disk problem?

[LeveL]

I just integrated the latest batch of hotfixes with nLite.

I started off with a full Windows XP SP2 and integrated

all hotfixes that nLite could integrate. Then after installing

I went to Windows update and needed these...

IE7-KB928090-WindowsXP-x86-enu.exe

WindowsXP-KB918118-x86-ENU.exe

WindowsXP-KB924667-x86-ENU.exe

WindowsXP-KB926436-x86-ENU.exe

WindowsXP-KB927779-x86-ENU.exe

WindowsXP-KB927802-x86-ENU.exe

WindowsXP-KB928255-x86-ENU.exe

WindowsXP-KB928843-x86-ENU.exe

WindowsXP-KB931836-x86-ENU.exe

These only came out yesterday (13th February 2007)

So again I took my SP2 from scratch and integrated all hotfixes

with the addition of the new hotfixes listed above. I didn't do it in

two stages, I integrated all of them in one go.

Now when I install XP (in VMware) it copies all the files to the hard disk,

then reboots and as soon as it has rebooted I get this message:

lsass.exe

A write operation was attempted to a volume after it was dismounted

Then setup reboots in an endless loop, the above error only pops up for a split second,

I had to pause VMware at the right time to read it.

After Googling this and finding out it could be a power supply or RAM problem,

I deleted my VMware virtual disk entirely and recreated it. I still got that same

error on a newly created VMware disk.

I then tried another XP ISO I had made a while ago and it worked fine. I have

tried about three different ISO's of various XP installs and they all work fine, so

it is certainly the very latest batch of hotfixes that are causing this. All the other

installs I tried were stripped out edition, all of them had hotfixes slipstreamed too,

just not these very latest ones.

I am integrating an IE7 hotfix although IE7 is not slipstreamed or added - could this cause it?

Although now altogether there are two IE7 hotfixes, I already WAS integrating one of them

without problems.

The only other thing I can think of is the disk size - I only use a 3Gb VMware disk but

I do not see why any hotfixes should require you to have a larger disk than 3Gb.

I will try with another freshly made VMware hard disk @ 5Gb and post back the results.

Has anyone else integrated these latest hotfixes? Can anyone confirm this is the case

on their system or it is just my crappy power supply? It has been on the blink for two

weeks, I need a new one. But then, like I said this is only happening if I

integrate/slipstream the above list of latest hotfixes.

Edited February 14, 2007 by LeveL

[LeveL]

It happened because of:

IE7-KB928090-WindowsXP-x86-enu.exe

Its a big Hotfix - 7.48 MB

Doesn't matter if you have IE7 integrated or not, it still happens.

I will try integrating IE7, then let nLite complete the integration

of IE7, then run it through nLite again - adding that one

Hotfix. Although I did have the IE7 addon listed to be integrated

before the IE7 Hotfix in nLite and still got that error.

Can I just ask - if you have IE completely removed, you don't need

any IE7 Hotfixes?

[LeveL]

LOL, Boooggy and Nuhi reading the topic!

Yes the IE7 addon is by Boooggy.

The problem seems to be that it is adding IE7 files that arn't needed.

That KB928090 has an IE6 version and an IE7 version...

Cumulative Update for Internet Explorer for Windows XP Service Pack 2 (KB928090)

Cumulative Update for Internet Explorer 7 for Windows XP Service Pack 2 (KB928090)

See how the two versions ARE the same hotfix, its just that one is for IE6 and one is for IE7.

By the way I have integrated the IE6 version of this hotfix in nLite just now and it is fine.

I will just have to be careful depending on whether I am integrating the IE7 addon

(the browser itself) or not - but remember though, even if you are integrating this

IE7 addon (the browser itself) and the IE7 hotfix - then you will get the error...

lsass.exe

A write operation was attempted to a volume after it was dismounted

Shizen... I will have to add it as a manual (but silent) install, its just that it adds

more than 7Mb to the ISO because its a big one (Cumulative hotfix)

Edited February 14, 2007 by LeveL

[boooggy]

sorry level i didnt make any ie7 addon.......

[LeveL]

sorry level i didnt make any ie7 addon.......

Sorry boooggy I thought you did

Now i'm wondering where I got it from.

Regardless of who made it, its because I was trying to stuff an IE7

only hotfix into a source that does not yet have IE7, hmmm, I will

work this out somehow... I hope.

[nuhi]

I just tested IE7 (installer from ms) + KB928090, integrated with nlite, all removed with ie compatibility ON and all works ok.

[stimpee]

I just got this exact same error but looking at my list of hotfixes I dont see the 928090 in there.

I did however see the 933566 and 929969 IE7 fixes so i removed those and now I'm having another attempt at writing.

Using WUD to download the full list of post-SP2 fixes, removing all the IE7 hotfixes then integrating with nLite.

EDIT: And now it worked just fine. I also removed the IE7 compatibility check box.

Edited July 13, 2007 by stimpee

[nuhi]

stimpee, if you manage to repeat the issue let me know how, thx.

[DL.]

I get that error message too, but also a few others with lsass.exe.

They say something about:

-system resources

-virtual memory

(It's alternating between those three I think.)

In my first try I didn't integrate KB928090 (must've missed it when downloading the hotfixes), then I've tried integrating both versions of it separately one by one.

I've tried with both VMWare and real HW, but the problem still remains.

I'm using the latest version of nLite and XP Pro.

[nuhi]

Enable Hotfixing reports in the Advanced options on that page, then if you see that some hotfix is having too much older files check if you really need it.

Then be sure to sort all hotfixes by their build dates and that IE is integrated before IE hotfixes. Top is first.

[RJARRRPCGP]

Sounds like possibly permissions problems. Sounds like possibly the required permission settings aren't there.

Edited July 17, 2007 by RJARRRPCGP

[johnwinterflood]

I would just like to confirm that I am having the exact same problem that LeveL has reported. However I do not have IE7-KB928090-WindowsXP-x86-enu.exe in my list of hotfixes (and neither do I have either of Stimpee's IE7 fixes - 933566 and 929969). Also I am having this problem trying to install from a CD to a real formatted hard drive (not a VmWare simulation). Like LeveL I recently reinstalled a system (actually WinXP on a MacBook Air) and noticed that it wanted about 22 more hotfixes than I had already slipstreamed into XP3. So I noted their names, dowloaded them all, and slipstreamed the whole lot into a new installation CD for a desktop which is now showing the identical symptoms to LeveL's. Here is the list of XP3 hotfixes that I integrated:

WindowsXP-KB923789-x86-ENU.exe

WindowsXP-KB938464-x86-ENU.exe

WindowsXP-KB941569-x86-ENU.EXE

WindowsXP-KB942763-x86-ENU.exe

WindowsXP-KB946648-x86-ENU.exe

WindowsXP-KB950762-x86-ENU.exe

WindowsXP-KB950974-x86-ENU.exe

WindowsXP-KB951066-x86-ENU.exe

WindowsXP-KB951376-v2-x86-ENU.exe

WindowsXP-KB951698-x86-ENU.exe

WindowsXP-KB951748-x86-ENU.exe

WindowsXP-KB951978-x86-ENU.exe

WindowsXP-KB952287-x86-ENU.exe

WindowsXP-KB952954-x86-ENU.exe

WindowsXP-KB953839-x86-ENU.exe

WindowsXP-KB954211-x86-ENU.exe

WindowsXP-KB954459-x86-ENU.exe

WindowsXP-KB954600-x86-ENU.exe

WindowsXP-KB955069-x86-ENU.exe

WindowsXP-KB955839-x86-ENU.exe

WindowsXP-KB956391-x86-ENU.exe

WindowsXP-KB956802-x86-ENU.exe

WindowsXP-KB956803-x86-ENU.exe

WindowsXP-KB956841-x86-ENU.exe

WindowsXP-KB957097-x86-ENU.exe

WindowsXP-KB958644-x86-ENU.exe

WindowsXP-KB958687-x86-ENU.exe

WindowsXP-WindowsMedia-KB952069-v2-x86-ENU.exe

In addition I Added the following IE7 files (in this order I believe)

IE7-WindowsXP-x86-enu.exe

IE7-WindowsXP-KB938127-v2-x86-ENU.exe

IE7-WindowsXP-KB953838-x86-ENU.exe

IE7-WindowsXP-KB960714-x86-ENU.exe

WindowsXP-KB958215-x86-ENU.exr

I then included a couple of addons:

Java Runtime Environment 6 Update 11.cab

and a DotNet 2 thru 3.5 that I built using someones tool.

I then added WMP11 (which itself needs 3 hotfixes) by running the dedicated slipstreamer after finishing the nLite run. The WMP11 files I included were:

wmp11-windowsxp-x86-enu.exe

WindowsMedia11-KB929399-v2-x86-INTL.exe

WindowsMedia11-KB936782-x86-ENU.exe

WindowsMedia11-KB939683-x86-ENU.exe

At some stage I also added some drivers for a particular machine but I don't remember if I added them in the first nLite run or added them later (to tailor this distribution to a particular machine).

Fortunately I decided not to install it on my main hard drive, but thought I would try it first on a second drive which I could format for the purpose. I unplugged the main drive so that it wouldn't go searching for previous installations etc. So that is my story and I may be able to do some experimenting with it if that would be really useful to nuhi or someone. Any clues anyone can suggest as to which new hotfix might be causing the problem would be greatly appreciated!

Edited February 21, 2009 by johnwinterflood

[johnwinterflood]

OK it seems that my problem is solved - and here is what I did. I left the entire list of hotfixes the same, but just reordered them by their build dates according to nuhi's instruction. Since a few of them (IE7 and addons) didn't have build dates, I ensured that IE7 was first and the addons last with the rest in between according to their build dates. I also turned on warnings and these were the ones that I got:

While integrating IE7 it came up with the following "Newer file already present warnings":

browseui.dl_ - File is newer than the one integrating.

File version in ISO: 6.0.2900.5512

File version in hotfix: 6.0.2900.2995

jscript.dl_ - File is newer than the one integrating.

File version in ISO: 5.7.0.16599

File version in hotfix: 5.7.0.5730

shlwapi.dl_ - File is newer than the one integrating.

File version in ISO: 6.0.2900.5512

File version in hotfix: 6.0.2900.2995

vbscript.dl_ - File is newer than the one integrating.

File version in ISO: 5.7.0.16599

File version in hotfix: 5.7.0.5730

Following that I got the following warnings:

KB941569 - Direct integration for this hotfix is not supported.

KB942763 - Direct integration for this hotfix is not supported.

KB946648 - Direct integration for this hotfix is not supported.

(msgsc.dll - File is not present in the ISO to be updated.)

KB938127 - Direct integration for this hotfix is not supported.

KB953839 - Direct integration for this hotfix is not supported.

KB953838 - Direct integration for this hotfix is not supported.

KB956391 - Direct integration for this hotfix is not supported.

While integrating KB958215 I got the following "Newer file already present warnings":

mshtml.dll - File is newer than the one integrating.

File version in ISO: 7.0.6000.16705

File version in hotfix: 6.0.2900.5694

urlmon.dll - File is newer than the one integrating.

File version in ISO: 7.0.6000.16705

File version in hotfix: 6.0.2900.5694

wininet.dll - File is newer than the one integrating.

File version in ISO: 7.0.6000.16705

File version in hotfix: 6.0.2900.5694

And finally:

KB960714 - Direct integration for this hotfix is not supported.

I thought I would try installing it before slipstreaming WMP11 and it installed OK and seems to run fine. It came up with one file that it wanted to download and install - KB808461 which "installs a permanent copy of the Package Installer". So I guess this must be a very late addition?

Since it did not list any of the hotfixes for which "Direct itegration is not supported", I suppose that answering yes must have caused them to get installed by some means? Anyway it seems that I now have a system that boots and really the only change I made would seem to be reordering the hotfixes and leaving WMP11 out.

[johnwinterflood]

... It came up with one file that it wanted to download and install - KB808461 which "installs a permanent copy of the Package Installer". So I guess this must be a very late addition?

But apparently this is an ancient addition - released in June 2005!!. So why is it wanting to download this one. Surely this must have come in with SP2 or at least SP3?

Anyone else's machine trying to download this ancient update? Any clues why?

[DaveKimble]

Getting the dates of the fixes in the correct order fixed it for me. This is made more difficult because some fixes have dates as yyyy-mm-dd (which is sensible), some have mm-dd-yyyy, and some have a blank date. This should be explained better in nLite.