Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Well, I have an old Dell Dimmension XPS R450 that had a HD crash. I replaced the HD with a WD 10GB and got this error,
c:\windows\system\vmm32.vxd: missing unable to load.I have tried everything from a dozen sites and suggestions and the simple switching of CD-R boot to after HDD boot was all it took.
*sigh* 2 days of wracking my brains, pulling out all the peripherals, changing CD's, changing HDD's, attempting complex edits of the VMM32.VXD file... all for naught.
Why? Stupid MS ... ??
Annnnyways...
Thank you So Much for posting this fix.. even if the blasted thing makes No Sense, at least it works!Blessings
M < > <
"the simple switching of CD-R boot to after HDD boot was all it took."
That seems hard to believe.
Do yourself a favor BACKUP!
Sorry, I do not check for private messages
0 
My mind is mystified (but I'm getting used to it)
We've heard that a million monkeys at a million keyboards could produce the complete works of Shakespeare; now, thanks to the Internet, we know that is not true
0
Yeah, me too. Usually you end up reloading Windows on top as a minimum.
NOTE: Take a copy of vmm32.vxd and put it on a floppy. It can save you a lot of hassle. Resave it after hardware changes.
DerekW
0
Thanks for posting that fix but unfortunately it only works on Fridays in May in even numbered years.
0
http://www.easydesksoftware.com/news/news10.htm
http://support.microsoft.com/?kbid=191874
remember:VMM32.vxd is the virtual device driver library that contains virtual device driver files needed for system start up, so VMM32.vxd is different for every machine; therefore, if it gets corrupted, it cannot be copied from another computer; it'll need to be rebuilt.
thanks for sharing
0
Actually, in many cases, copying it from another computer works just fine. I can't say it will work everytime but look at it this way:
Vmm32.vxd is created when you do the initial installation. You can install, remove or change all the hardware you want, even the motherboard, and it stays the same. After all the changes the system is just as different from the way it was originally as if it was a different computer. Yet vmm32.vxd is the same.
I believe this is because hardware changes that would normally change that file instead add whatever files are necessary in the windows\system\vmm32 folder.
0
Yes DAVE, I was being guarded in my #3 when I said about resaving copy of vmm32.vxd after hardware changes. In fact I've never known mine change either.
In recent times I've changed my view about copying vmm32.vxd from another machine with the same OS. Seems like it usually does the trick.
DerekW
0
I just had the same issue on a Dell XPS 400 series a customer brought in for service. After changing the boot order (following many attempted reinstalls) this fixed the issue. I don't know how, but it works.
0
Thanks for posting in. I guess the more a person learns about computers the more it becomes apparent they have their own personalities.
0
Harping back on the chat about using vmm32.vxd from another machine. I have records of "all" the files this contains (from registry) both before and after I changed my mobo a few years ago.
There were quite a lot of differences, so I guess your level of success in using vmm32.vxd from another machine might depend upon the similarity between motherboards.
DerekW
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
