About once per day, I am being requested to install 2 Windows updates in Parallels. They are always the same ones (KB890859 and KB931784). This repeated request to install updates does not occur in Boot Camp--only in Parallels. Does anyone know how to eliminate this? Thanks for any help. James
I saw on a thread on this... Let me know if you can find it by searching... I'll look tomorrow if you can't.
http://windowsxp.mvps.org/890859.htm I would try the same process for both updates. you could also read this, tho it contains much the same info. http://forum.worldstart.com/showthread.php?t=107821
Look into a subsystem called "Windows File Protection". There is a hidden directory under \system32\ that holds backups. Make sure that your update is updating both the update AND the backup. Also, preform the update in safe mode if you can... Reading information out of the backup directory in normal mode does not always do what one would think...
I have the same symptom but both the system32 version and the dllcache versions for those files are 5.1.2600.3093 so I'm not sure that's the file that is getting replaced. I did notice that the version in system32 has an extra underscore in the name so perhaps it is the issue. I have repeatedly reported the problem to Parallels support, but the responses I got showed they either didn't even read the support ticket or they are completely ignorant of stuff that anybody doing tech support for windows related things should know. I got great replies such as "Please go to Configuration Editor -> CD/DVD-ROM -> check Use CD/DVD-ROM Drive if it isn't checked -> OK -> start Windows -> maybe it will help. " "It is well-know problem with activation some software on VM from Boot Camp partition. We working hard on it, but now we only advise to address to company you purchased software and explain, that you use the same computer with it. " and finally "Please explain me what is KB890859?" I finally gave up. If someone figures out what is going on and a solution, I'd love to hear it. Right now I either deal with the long shutdown time while it applies the patch, or the next time I boot it applies the patch anyways and then forces a reboot.
doing a google will show you that these updates repeatedly requiring install in indeed a windows problem. Lots of people have had this problem who arent running parallels.
Well, since Parallels shows up the hardware in the same way for each install, it seems that the way Parallels virtualizes things is the way that gets the loop. And thus, since it is the same on every single one, all Parallels users are hit. It IS an issue outside of Parallels, I have had this on another computer (it's long fixed so I don't remember the manufacturer).
no i dont work for parallels... this has been discussed severla times on here, i thought I would just try to help you out.. no need to get smart with me.. heres a few examples of what i mean.. Searching for the phrases "KB890859" and repeatedly, does bring up the parallels link as the first one.. but only the first link.. http://www.certificationchat.com/archive/index.php?t-47315.html that appears to show the same problem NOT using parallels.. and again http://gabriel.lozano-moran.name/blog/PermaLink,guid,a188ee2d-fc12-4166-907d-0baf8b69572d.aspx this appears to show the other update doing the same thing.. again.. not on parallels... http://www.microsoft.com/communitie...&tid=07bcd14c-ba22-4715-97ef-0a91c2e594e2&p=1 and again.. http://forum.worldstart.com/showthread.php?t=107821 hmm look.. not using Parallels.. so maybe it really is a windows problem !?!?!?! I could post more if you need more evidence that this exists outside of Parallels....
Hello, We are aware of problem with these updates in current version of Parallels Desktop. Next release should solve this issue. Best regards, Mike
Thank goodness. It's driving me crazy asking to reinstall every day. Boot Camp never seems to need to reload these updates, only Parallels.
What I do is search for the KB file on my system. There should be an info file that you can read in notepad. Look at the file and determine if the update was successfully installed (many times it is not). If it was successfully installed and is still showing up as needing to be updated, manually go to the windows update site and tell it to never try to update that patch again. Works for me. j
There's one key question we seem to have skipped: is the system protected with these updates (even though it says it needs them again) or not? I'd be okay reinstalling them over and over if that's the right thing to do (until the fix comes from Parallels). What I *don't* want to do is hide the updates if I actually need them. Maybe Mike (who has quite helpfully acknowledged the issue) could add that bit of information? I know I'd find it helpful. Really I'm asking the more general question: what should we do in the meantime? Thanks.
Will there be another build of 2.5 that includes the fix for this bug, or will all of us 2.5 users be forced to upgrade to 3.0 to get the fix?
