Microsoft Vm Update

[gamehead200]

Whenever I install the update for Microsoft VM, it says that it will only update the existing VM files...Then, the next day, Windows Update keeps asking me to install it again...

This has been happening over and over again....Any ideas why>

[Tinker]

I had the same thing happen as well as others. I had to reload M$ VM to get it to work..

** M$ VM ** This is from the www.hongkongjockeyclub.com and should be O.K., however use at your own mindset......

[gamehead200]

So far so good...Haven't had any windows update pop-ups so far...

[Doggie]

same thing with me.. i just formated installed xp, then xp sp1 and it was fixed

[dr15]

Looks like I'm having this problem also.

I'm not positive, but I'm guessing it has something to do with this. And this.

Apparently M$ cannot distribute the M$ VM any more. And as of February 4, 2003 they are no longer including it in the SP1 service pack. They are, however, allowed to put updates out for it until January 2, 2004.

So here is my guess. If you are having this problem you probably installed Windows XP and SP1 after February 4, 2003. M$ puts out this latest patch which includes an update for M$ VM. Windows update downloads the patch and when you try to install it you get an error because you can't update the M$ VM if its not already installed on your computer. Since the install fails, the next day windows update goes and downloads the patch again.

I'm not positive this is whats going on. The above post from Doggie certainly refutes it. But it seems to make sense to me and fits in with my situation (a machine I built recently is having this problem yet an older one is just fine).

In any event, since M$ can no longer distribute the M$ VM, your gonna be forced to snag the file from someplace else (thanks Tinker). Personally, I'm not real comfortable with doing that. So for now, I'm just turning off the automatic updates. I'll just have to manually run the windows update and pick and choose until M$ figures out a bunch of folks are having this problem.

[edit] just removed a certain word and replaced it with what seems to be the common lingo...

[Tinker]

Here are a few more links for ** M$ VM ** ....

[asklepios]

dr15 you are absolutely right. after losing the suit to sun microsystems M$ can't provide JVM (Java Virual Machine). Doggie is right too that he installed SP1 and fixed the problem.

The thing is that after losing the suit M$ pulled out the JVM and launched another Service Pack called as SP1a. Anyone who have the full install of SP1 (133MB) can have JVM pretty easily while those who don't have it should try JRE by Sun Microsystems. I would certainly not reccommend having a VM from not so reliable source.

cheers