Replies

Yeah! That worked! Since the message said that it was looking for updates “on this computer”, it never occurred to me to disconnect. Thanks.

In the process, about a couple of dozen updates were installed including the “roll-up” as the last one. Perhaps 1/2 of them failed. the “roll-up” did OK. We’ll see if it gets back to the normal update process now. I have it set to download updates, but not install them.

I downloaded GWX and used it to disable everything having to do with Win10. I then downloaded KB3125574, the Win7 roll-up package, and tried to install it. The Windows Update Standalone Installer has been “searching for updates on this computer” for about 6 hours with no results yet. Do I shut it off or leave it running? Would I get better results using WSUSOffline?

Update:
As you instructed, I uninstalled the two problematic sticks and then re-inserted them one at a time. The first one (4gb) was found and assigned a drive letter without a problem. The second (16gb) was found by windows but it would not show up in “my computer”. However, I noted that it had been assigned a letter according to USBDview. As it turns out, as you suggested above, Windows was assigning it a letter that was already used by one of the shared virtual hard drives. Using Windows Disk Management, I manually assigned it a different letter and all is well. According to one of your links, that drive letter should be used from now on. I don’t know what caused the problem in only this particular installation but, at least, it is working now.
Thanks for all the help.

I have just completed a fresh install of disk #2 and all my usb devices are functioning normally in it. However, just for grins, I’m going to follow your advice to remove the entries and see what it does. I’ll let you know.

I skimmed through the two links and it looks like there could be some relevant information there. I haven’t tested them because the fresh install is working. But, I did keep the articles just in case. Thanks

The only thing I have readily available is the virtual drive. While I have another desktop, I don’t want to remove what is there now to test this. I’ll do another virtual drive installation to start with and see what happens. I’m also thinking about moving the data off of the two memory sticks and formatting them to see if that does anything positive.

I understand. However, remember that this only occurs if the sticks are inserted prior to bootup. Neither stick is recognized or assigned a drive letter if inserted after boot up even though USBDeview shows them as connected. Also, with VM #1 there is no problem at all. There each one is usually assigned drive H.

I downloaded and ran USBDeview. After inserting the 4gb usb stick it says that it is connected, not disabled, and is assigned drive F. It also says that the 16gb stick is connected and not disabled but it is not assigned a drive letter. Neither appear in “my computer”. With the sticks inserted during bootup (not at the same time), the 4gb is assigned drive F and the 16gb is assigned drive E. Both appear in “my computer” and are accessible. I’m not sure what other information provided by USBDview is pertinent to this problem.

I’m not sure what to check. As I said, there are two virtual machines running in Virtualbox on the same host with the two versions of XP. One has the problem. The other doesn’t. I didn’t mention another desktop machine also running XP that does not have the problem. But, it was not loaded from a slipstreamed disk, assuming that is pertinent. I suppose I could re-install virtual machine #2 to see if that does anything positive. My gut tells me that that is not the problem. There seems to be something peculiar about those two specific memory sticks because the other usb devices including the pny stick work OK.

No. I think I understand that part OK. I’m starting with my original disk that includes sp1. I’m then slipstreaming sp3. I understand that sp3 includes all updates that came before. I’m assuming that what I’m seeing in C:windowssystem2CatRoot… (after booting the slipstreamed disk) are all the updates from 0 to sp1, sp1 to sp2, sp2 to sp3 (all included in sp3), and post sp3 (downloaded from WUD).

That makes sense when I think about it that way. I did find what I assume are all updates from sp1 thru sp3 plus the ones I just added in C:windowssystem2CatRoot… Over 200 files there; mostly KB…

Just for grins I ran nLite again and put dotnetfx_35.exe ahead of dotNetFx40_Full_x86_x64.exe. Those two then integrated just fine. However, nLite then stumbled over another file related to wmp11 and tried to shut down again. I’m pretty sure that this is a different file than caused this the previous time. I guess I should report this to nLite.
Thanks for the help

Tonyl,
I may need to post this on the MSFN site but I thought that since you have been so helpful I would fill you in on what’s going on. I downloaded the latest updates list for XP from WUD and, as you said, it includes everything including critical, optional, media player, and .net updates. I inserted the list into nLite, organized them by date, made a few other adjustments, and started the integration process. Soon after starting a message popped up that said: “dotnetfx35.exe – Not expected type of hotfix”. Then, on top of it, another message popped up that said the system was shutting down in __ seconds. I was able to stop the shutdown and the process continued. A short time later, three other messages popped up saying that certain updates were being skipped because they are “not made for this Windows version”. I clicked “OK” for each one and the process continued to the end. I made a bootable CD from the ISO and used it to install on a virtual machine. It appeared that all was good until I checked to see if all updates appeared in the Control Panel-Add/Remove Programs window. The .net, optional, and Media Player updates are there but not the critical updates. There are only 3 under the category of security update.
The dotnetfx35.exe file loads the initial version of .net framework 3.5 among other things, I guess. DotNetFx40_Full_x86_x64.exe is also in the list and it was integrated just fine. Maybe the problem was that it was in the list ahead of dotnetfx35.
I don’t think that the other 3 “skipped” files indicate a problem. According to Microsoft, the 3 skipped files have multiple versions for x86, 64, win2000, Vista, etc. However, the 3 skipped files had “x86” in the name and they are for XP.
I checked the last run in nLite and there are about 140 hotfixes and security updates. I’m wondering why only 3 were integrated. On another machine we have with XP there are well over 100 security updates which were installed from MS in typical fashion.
The only “adjustments” I made was to eliminate the foreign keyboards and languages (thought it might save some space), put in my product key, and regional info. It doesn’t seem like that should have caused a problem.
Maybe the threatened shutdown caused it? I suppose I can switch the two .net files around and do another run (wasting another CD) :rolleyes:
I would appreciate any comments you may have.

Seems like I’ve looked every where. How did I miss that one? Looks like just what I need.
Thanks

Just a quick update:
Back when sp3 first came out, I followed some very good step by step instructions and made a slipstreamed disk to include sp 1, 2, & 3. It worked fine and I’ve used it on a couple of occasions. When I decided to make another disk to include all of the post EOS critical updates I thought that the first slipstreamed disk was a logical starting point. As I mentioned above, the second one didn’t work. I decided to try again using my original sp1 disk as a starting point. This time it worked just fine and I used it to do an install onto my virtual drive. All is going well with it so far.
I’m still working on being able to store and install all the .net framework fixes and updates offline. I found that there are 3 executables that will install the basic versions 1 thru 4 offline. But, that leaves lots of fixes and updates; some of which require a connection. I understand that there is a beta version of “unofficial” SP4 out there. I’ve read a few pros and cons. There is also a download file named .Net Framework AIO. I don’t yet know how to use it.

That’s kinda what I thought. I’ve been having trouble getting a good slipstream done. I think I’ll just stick to the image for now.
If you don’t mind. Maybe you could answer a question about my slipstreaming problem:

Using nlite on my old WinXP system, I created a bootable disk that included all service packs and all updates since the last one. I used UDC to download the updates. The disk booted OK on the XP machine and I let it load everything up to the setup screen (didn’t want to overwrite anything). I have Virtual Box running on my Linux laptop and tried to use this for a test install of XP using the newly created disk. The disk booted but very quickly stopped with the message “i8042prt.sys could not be found”. I did a search for the file and found it in i386sp3.cabi8042prt.sys on the DVD. Any idea what went wrong and what I might do differently?

If I use the image backup to re-install I can easily delete the software included with it and install something new/different. Can you tell me what you mean by “change any other software”? Why is it better than using the image? Maybe I still want to do the slipstream process and just don’t know it yet:rolleyes: