Forum Discussion
1492
Jul 18, 2015Moderator
This may explain why you're having difficulty finding MS Malicious Program Removal Tool. MS has cancelled security and signatures updates for MSE and the Malicious Program Removal Tool for WIN XP. See Windows XP Security Just Got Worse Again.
There are some enterprise environments still using WIN XP, but are paying MS for continued security support. I know of one WIN XP box in our organization, mainly for using an outdated version a word processing software, but it is not allowed to be connected on our enterprise network. In fact, doing so will have its ports blocked as it can compromise security on the network as a whole.
In fact, I just received an exception for 30 days for a Windows 2003 server box running outdated CA software, which just went end of life on July 14. This to allow me to port old files over to a new app running on Red Hat Linux enterprise server cluster. Though intend to have this complete, and this WIN 2003 server disconnected way before the exception runs out.
You generally have a limited time after end of life security support before vulnerabilities begin to show up. As hackers take ready advantage of lack of OS patch support to exploit vulnerabilities.
If I had to run WIN XP, then I'd have many more layers of security than just AV and firewall. Luckily, I don't need WIN XP, and run a current fully supported OS, but still have 5 layers of security. But more importantly, have multiple recovery systems setup. For one primary reason. That you cannot guarantee against not being hacked. It's more a matter of when, and not if?
You can have locks on your doors and windows, but that doesn't stop a determined burglar from breaking into your house. Continuing to run WIN XP on the NET is like leaving the front door open. It's just a matter of time before someone comes along, and takes advantage of it.
There are some enterprise environments still using WIN XP, but are paying MS for continued security support. I know of one WIN XP box in our organization, mainly for using an outdated version a word processing software, but it is not allowed to be connected on our enterprise network. In fact, doing so will have its ports blocked as it can compromise security on the network as a whole.
In fact, I just received an exception for 30 days for a Windows 2003 server box running outdated CA software, which just went end of life on July 14. This to allow me to port old files over to a new app running on Red Hat Linux enterprise server cluster. Though intend to have this complete, and this WIN 2003 server disconnected way before the exception runs out.
You generally have a limited time after end of life security support before vulnerabilities begin to show up. As hackers take ready advantage of lack of OS patch support to exploit vulnerabilities.
If I had to run WIN XP, then I'd have many more layers of security than just AV and firewall. Luckily, I don't need WIN XP, and run a current fully supported OS, but still have 5 layers of security. But more importantly, have multiple recovery systems setup. For one primary reason. That you cannot guarantee against not being hacked. It's more a matter of when, and not if?
You can have locks on your doors and windows, but that doesn't stop a determined burglar from breaking into your house. Continuing to run WIN XP on the NET is like leaving the front door open. It's just a matter of time before someone comes along, and takes advantage of it.
About RV Must Haves
Have a product you cannot live without? Share it with the community!8,798 PostsLatest Activity: May 01, 2025