STOP error after installing Update Rollup 1 for Windows 2000 Server
- Hello, I'm having a problem with a clean install of Windows 2000 Server as a guest under Windows Server 2008 R2. I installed from the original disk and updated to SP4 via network install file. All other updates were applied via WSUS. Here's the order everything was installed with reboots between each:
Clean Install
SP4 Upgrade
Install Integration Services
Joined Domain
Install Updates
Using snapshots, I was able to narrow it down to Update Rollup 1 for Windows 2000 Service Pack 4 (KB891861). Without this pack, the server runs fine, but if I install it, I get the following STOP error on next boot.
STOP: 0x000000CE (0xEB040000,0x00000000,0x80458399,0x00000000)
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
This driver may be at fault :vmstorfl.sys
Address EB040000 base at EB040000, DateStamp 00000000 - vmstorfl.sys
Address 80458399 base at 80400000, DateStamp 384d9b17 - ntoskrnl.exe
I noticed this update pack has some SCSI related known issues, but the KB article notes a different stop error. Is this a Hyper-V specific problem?
Answers
Hi Suamme,
This is an issue that we just identified. There are some confliction with the Update Rollup 1 for Windows 2000 SP4 and Integration Service. To workaround this issue, please choose one of the following options:
1. Do not install Integration Services.
Or
2. Install Integration Services after you run all the updates.
We will release a public Microsoft Knowledge Base article for this issue soon. Thanks.
Vincent Hu
- Marked As Answer byVincent HuMSFT, ModeratorFriday, October 23, 2009 7:14 AM
All Replies
What if you slipstream in SP4 and the rollup into a distribution location or bootable ISO and then try the install? I wonder if the order of operation of the installation of the integration components vs the update have any affect as well? I will try this on my Hyper-V test lab to see what happens.
Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP Managing Consultant VSD TechnologiesI managed to run into this same issue with Win2k SP4 with Hyper-V, hopefully there is a solution.
I tried to recreate the problem on my test server and no luck. I installed W2K SP4 then the integration services and then the update and no BSOD. I then installed W2K SP4, SP4 Rollup and no BSOD. This is on a R1 server I will test on R2 in the morning.
Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP Managing Consultant VSD TechnologiesHi Suamme,
This is an issue that we just identified. There are some confliction with the Update Rollup 1 for Windows 2000 SP4 and Integration Service. To workaround this issue, please choose one of the following options:
1. Do not install Integration Services.
Or
2. Install Integration Services after you run all the updates.
We will release a public Microsoft Knowledge Base article for this issue soon. Thanks.
Vincent Hu
- Marked As Answer byVincent HuMSFT, ModeratorFriday, October 23, 2009 7:14 AM
- Is there anything that can be done on the host machine to prevent this from happening? I can dig out a backup, but what a pain. Not good testing Microsoft.
Hi,
You can refer to:
You receive a "Stop 0x000000CE" error on the restart after you run Windows Update on a virtual machine that is running Windows Server 2000 SP4
http://support.microsoft.com/kb/976488/en-us
Vincent Hu
- OK, but I suspect most people will run across that KB After the damage has been made. I was doing some upgrades of 3 of our Win2K VMs and got bit hard by this bug.
