I am having a huge problem with XPmode
XPmode starts, I get a black screen, then if I move the window it will start enabling integration features. It then either fails to load them and says I can log into it without them (a pointless procedure as it can't then see the network) or else there is a flash as a dialogue box appears for a split second and then vanishes behind a completely blank blue screen. No programs load when that happens. If I click on the menu at the top it says that the features ARE enabled (at least the drop down has an option to disable them which you only see when they are enabled) but I can get no response from the window unless I try resizing it, at which point it starts enabling integration features again.
My XPmode is set to close down completely when I close it. It does not hibernate because I only need it occasionally, but when I need it, I need it. Windows 7 Ultimate 64 bit 16gb ram, with Intel Xeon CPU E3-1240 V2 @ 3.40Ghz dual core. I have 3330gb ram assigned to the Virtual machine. I have the XP firewal set to allow everything through as some say that can block integration features but that did not make a difference.
I have looked at other similar tiopics but all seem to assume that people normally let XPmode hibernate, and say that the answer is to close it completely. I ALWAYS close it completely. We got it working after a struggle when we first installed it, but now it is completely useless and I have to go to another PC to use legacy programs.
Deleting Windows XP Mode.vsv is not the answer because this file removes itself when you closedown the program properly. I can't delete what does not exist.
I have tried using win7 task manager to kill process and task, as some have advised. Makes no difference.
I found a solution to an almost identical problem on our previous installation of XP mode which I vaguely recall involved editing something in a Win7 registry file, but I cannot now find that website with that information again.
Is reinstalling XPmode the only soilution? we had a terrible time installing it in the first place and it never could interact with local drives although we did get it seeing our network.