Recent content by Stompem

VMWARE has updated and the workaround is no longer required and VM integration is now working OK. IMO if you've hidden the Windows Update in question you can now safely re-install it to update your system and fix the memory leak.

Sounds pretty tough... hope the EXE isn't corrupt. Refreshing or even Reinstalling seems to be the only conventional way left unless someone else can help but... I'm in no way suggesting you use 3rd party open source software but this is probably what I would do. I'd burn a Ubuntu ISO (x86...

Try these as they shouldn't hurt anything if they fail: Use the rescue disk or original installation disk to boot to a Command prompt - bootrec.exe /FixMbr bootrec.exe /FixBoot bootrec.exe /RebuildBcd Edit: Usually the commands are done in the order above, each a higher level of support...

@Tovad Thank you for posting that particular workaround It still leaves a point in question as to whom has the onus to correct this anomoly, Microsoft or VMWare? It would be interesting to pinpoint the exact cause of the memory lockdown for future reference and troubleshooting as there may be...

Yes that's the culprit. I had the same errors, I started the VM just after the update and so it was a lucky guess that KB 2995388 was at fault. Fixing a memory leak was one of the main objectives of the update according to the MS literature. LOL!