The Security Update for Windows XP (KB2676562) has spoiled my weekend. My Windows XP cm was originally working fine with the integration features but out of sudden the integration features are disabled. I cannot connect USB devices inside my vm anymore.
I tried the solutions found in the internet but no luck at all. It left me no choice but to delete the windows update that applied before the integration features was working fine one by one. And I found out that KB2676562 is the root caused. If you bump into this problem, please delete this patch and you can see lights again.
I can now resume my Diablo 3 again. =)
I just noticed I have this problem too. Host machine is Win 7 home premium, running is XP Pro SP3 inside Virtual PC 2007 SP1[1]. VPC's settings have Adapter 1 pointing to host machine's WiFi. It worked fine until a few days ago, when network connection in the VPC started showing "Limited or no connectivity" & I assume the security update caused the issue. Has MS issued a fix or a workaround for this yet? (ranting about microsoft follows below)
ReplyDelete[1] Am I the only one who feels Microsoft has completely RUINED Virtual PC? Where Virtual PC 2007 SP1 is straightforward and works like you expected, Windows Virtual PC is thoroughly confusing and kludgey to use. I'd been using MS's Virtual PC since the 2004 edition - when VPC 2007 came out it was a solid improvement. However with Windows Virtual PC (why couldn't they just call it Virtual PC 2009?), after taking lots of time to read the docs/blogs/etc. & jumping thru all the hoops to get it to do the things that were simple in 2007 (ie merging undo disks to the VHD, doing a simple shut down or restart of the virtual pc w/o access issues, just getting into a vpc's settings by having to go to the physical subfolder for each vm "c:\users\[user]\virtual machines\[the vm's folder]\" & right-clicking the "[vmfile].vmc" & clicking Edit where before you could do that from a single central application) and putting up with it for 8 MONTHS I finally uninstalled and went back to VPC2007 and the pain immediately went away. It wasn't that I just had to learn to "do it right" - they really DID screw up an app that had previously worked great.
[2] Windows 7: no great improvement over XP, at least as far as the interface goes, let me tell you. I pray that they get Windows 8 right or I'm jumping ship to LINUX for real. What happened Microsoft? Have you truly lost your way without your leader, just as Apple did in the mid-90s? Wrong in so many ways from changing the basic user interface - either hiding by default or outright phasing out the standard menus (File, Edit, Tools, Help, etc.), forcing the awful Ribbon on us, trying to "protect" us from basic things like where our files are stored (introducing confusing "libraries" that hide where one's files are stored) thus helping to confuse the hell out all kinds of users from seniors to seasoned business users (ever hear the term "if it's not broke..."?), to the general philosophy & direction you've taken your app development platform & tools - programming is supposed to get EASIER as technology progresses and we move into the Future. Enterprise .NET 4.x C# may be "correct" and fine for C++ programmers, but it doesn't make customizing or quickly building tools ANY easier than VB6, VBA, QuickBasic, & classic ASP. It just makes a lot of work trying to keep up and understand the insane mess you've created), to the messing up the Windows OS itself - were redesigning the UI, changing the location of many menus & basic processes, ruining the classic file search instead of just improving & making it faster, dumbing down & wrecking the classic Windows Explorer & shell, & forcing people to re-learn basic stuff that did not need to be redesigned, really necessary? Windows 7 should have fixed these issues that started in Vista (SHISTA!), restored the familiar features (or at least added OPTIONS to CONFIGURE the OS to LOOK/FEEL/ACT LIKE past Windows the users had known). But unlike XP, which really did improve on past versions, Windows 7 is still as confusing and a pain as Vista was. It was like your attitude was not to help the users, but "they'll get used to it". Well screw you, too.
So please, for the good of the world, re-learn the wisdom you once knew so well: that backward-compatibility is really important, building on the past & not just wrecking it saves everyone a lot of time/money/pain from not having to re-learn basic tasks.