[Solved] 304 W7 64 Host, XP32 client+D3D Support=Bricked OS?

[Quirken]

I updated to 3.0.4 without a problem. Then I noticed during guest additions that there was experimental Direct 3D Acceleration support.

Naturally, this piqued my interest, so I checked the box, thinking if it didn't work, I could just uninstall the driver.

Well, when it says it replaces certain system files... I guess it wasn't kidding.

I can no longer boot into Windows XP, except in safe mode. If I'm in safe mode, then I can uninstall the guest additions... but it still won't boot.

The BSOD it gives me says something about DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

Thinking there might not have been enough video memory, I tried increasing memory. No luck.

Any suggestions either to fix this or how I can roll back changes?

[vbox4me2]

In safemode you can use a restore point to rollback.

[Quirken]

In safemode you can use a restore point to rollback.

Unfortunately, I can't, as I disabled system restore due to limited hard drive space and only a small number of changes that actually take place in the VM.

I also tried sfc /scannow, but it doesn't work in safe mode.

[vbox4me2]

Then your left with manually locating the drivers and renaming them until it boots.

[Quirken]

Then your left with manually locating the drivers and renaming them until it boots.

I could do that, but I have no idea what files to rename

[vbox4me2]

Unpack the installer, whatever it does is in there.

[Quirken]

I changed all the files that were in there, and it still won't boot except in safe mode =/

[Quirken]

Windows starts booting, then it BRIEFLY shows the login screen, then I get this:

[Quirken]

Hmm. Google search on intelppm.sys turned up this: http://blogs.msdn.com/virtual_pc_guy/ar ... 84461.aspx

While VirtualBox is definitely NOT the same as Virtual PC... this indeed fixed my problem.

Which begs the question... why did the experimental video drivers install this?

(EDIT) And weirdly enough, after doing what it said on that link, I reinstalled the experimental driver... and it worked fine.