![]() ![]() That is almost two thirds of the size of the main Win 7 Windows installation. I wanted and still do to keep it as lightweight as possible as I'm using a fairly small SSD and the VM + XPMode now uses over 25+GB. The XP installation as I said is actually XPMode basically a free for certain Win7 versions cut down copy of XP. It was later that year it stopped working - likewise with no warning from MS. The XP installation was not done until several months after that, it appears to have been some time in July. I definitely know the updates, or at least the manual enabled updates direct via MSE, were working after 2015 because I actually had not built the PC concerned until 2016! I suspect this is quite a niche issue but if anyone else here has had this problem and or can suggest a sensible course of action I'd like to know. This is, as I say, new behaviour and why it has worked once (14 days ago) but not for the two weeks before or the two weeks since suggest this is some MS problem and they've changed something knowingly or unknowingly. Just doing that triggered MSE to start reporting my system as 'possibly unprotected' and I had to use a restore point to get it back to its previous state just reporting the AV definitions as out of date. ![]() I didn't want to end up not being able to install it or installing it and not being able to install any AV definitions. I thought about trying a reinstall of MSE but when I checked the current specs required for the latest MSE version I saw that WinXP was not mentioned so I reversed out. Obviously I've tried redownloading the definitions and reinstalling many times but MSE's definitions still will not report as updated. But since this problem arose MSE is still showing the definitions have not been updated, now for 14 days. This I've always taken to mean that it is being installed. It looks as if they are installing, when I click to launch it I still get the familiar WinXP egg timer which shows the updater is running, a short delay and then that comes back again. However recently, in the last five weeks, during the weekly updating I do it has refused to install the definition updates 4 times out 5. Occasionally I download it direct to the VM. There has been very little trouble with this, usually I use the host machine to download it and transfer that to a shared volume with the XP Mode VM. In April 2016 (?) automatic AV definition updates to MSE stopped and also could not be enabled manually via the update button but, as recommended, if you went to the MS web site you could download the appropriate MSE 32bit AV definitions update (mpam.fe) and install them manually. This is about the only situation now I would even dream of using MSE. I have used MSE (Microsoft Security Essentials) on that XP Mode system since it was installed - perfect, unobtrusive, small footprint and does its job. Heads up… I also hope to do a details blog about how to use Group Policy to configured WSUS in the future.I have Windows XP Mode (32bit) running on a virtual machine. I know this is not strictly a Group Policy, but WSUS does rely upon Group Policy heavily and therefore I find many Group Policy admin’s are also the WSUS admin’s for their organisations. This Microsoft blog specifically calls this being done for educational institutes that have low cost PC’s connected to their network. While most corporation probably will not have MSE deployed in their environment it might still be worth while to enable to ensure any fringe cases of computers on the domain are still being secured. This now allows any corporate that is running WSUS to centrally deploy pattern updated from a single server. Microsoft have now started to release definition updates to Microsoft Security Essentials (MSE) via WSUS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |