- Mar 15, 2014
- 347
- 43
- 91
I use Windows 7 XPMode on a VM. The parent OS of course has a full AV protection but I needed an AV for XPMode that didn't cause any conflicts. So as an AV with small footprint and no issue running on a VM Microsoft Security Essentials seemed like and was a good choice. It installed fine and works perfectly.
The AV definitions (updated manually) from the GUI also worked and I had no problems at all until around April this year when the download progress bar kept on stalling at the same point. It went back to the main window with the 'helpful' news that the definitions were now out of date and the "machine potentially unprotected".
I retried multiple times, turning on/off auto-updates until giving in and going for a full definitions manual download from MS and install. Worked perfectly, definitions updated, all good. Problem is that since then that is only way I appear to be able to update MSE now.
I tried reinstalling MSE, which was a mistake because I used the latest version which I didn't see now doesn't support XP. So I went back to the last version that did, reinstalled it OK but then ran into exactly he same problem as before.
What I don't understand is why? MS don't support XP I get that but this is just an AV definitions update matter. The definitions pack download will update the version of MSE I'm having to use in XPMode so why the hell can't I download it and install it either automatically or via the MSE GUI?
As said, there were no issues until a couple of months ago so this is new behaviour which others users are also reporting. MS has messed around with something and in doing that compromised a legitimate and, arguably, only sensible use of their own security tool: MSE with a still supported MS OS software ie. Windows 7 XPMode.
The AV definitions (updated manually) from the GUI also worked and I had no problems at all until around April this year when the download progress bar kept on stalling at the same point. It went back to the main window with the 'helpful' news that the definitions were now out of date and the "machine potentially unprotected".
I retried multiple times, turning on/off auto-updates until giving in and going for a full definitions manual download from MS and install. Worked perfectly, definitions updated, all good. Problem is that since then that is only way I appear to be able to update MSE now.
I tried reinstalling MSE, which was a mistake because I used the latest version which I didn't see now doesn't support XP. So I went back to the last version that did, reinstalled it OK but then ran into exactly he same problem as before.
What I don't understand is why? MS don't support XP I get that but this is just an AV definitions update matter. The definitions pack download will update the version of MSE I'm having to use in XPMode so why the hell can't I download it and install it either automatically or via the MSE GUI?
As said, there were no issues until a couple of months ago so this is new behaviour which others users are also reporting. MS has messed around with something and in doing that compromised a legitimate and, arguably, only sensible use of their own security tool: MSE with a still supported MS OS software ie. Windows 7 XPMode.
Facebook
Twitter