It's the reason I do all of my online activities via a sandbox Wallace. I run an XP VM to browse and even within the VM, I run Sandboxie so I'm double-sandboxed. I still used privoxy and chameleon (a program that blocks super cookies) but still, you are right. There's no such thing as perfect protection. I just run Defender (it's free so why not) in my host OS. Try to never browse using the host OS and do my best to vet any programs I install on my host. I regularly recover my VM to a golden state so, even if I get a drive-by infection, it's completely gone. My method does not protect against keyloggers, so I still have to be careful. It's worked for me (and verifiably protected) my OS on a number of drive-byes over the years including when MediaMilitia's site (site where I got my skulls) got infected.

IMHO... what you do to safeguard your machine is more then most are willing to do and or even know how to do.
I consider myself lucky to not have encountered any issues with my machine's security being breached. Although this still remains to be seen.
Keyloggers are especially difficult to deal with. I have never found them on any of the machines I've ever had, but this may also mean that they may have been present and I just didn't/couldn't detect them.

I agree; it more than most are willing to or know how to do. Supposedly, modern browser do implement some sandbox mechanisms, but there's no comparison to a true sandbox. Also, since the sandbox flow isn't widely use, most mal-ware folk won't even bother wasting their time on trying to infiltrate such a protection scheme since it buys them nearly nothing at all. Win for me. I have 8 cores and my system supports virtualization so needless to say, my XP runs faster then any native XP machine I've ever encounted. It even boots up in about 12 seconds. lol

I know there's going to be a day when no one will support XP anymore. So far that day's not come yet. Just grateful that there are browsers that support HTML5 that work in XP (like Iron which I now use as my main browser thanks to Moko who shared this browser with us a few years back).

One other thing; the powers that be still haven't ported Autotrace to Win7 and above; it still works perfectly fine in XP.

I don't know the actual technical reason for the warnings but I have gotten them several when trying to download scrips and programs. Contacted Norton, my antivirus program and it was explained to me that some programs are not recognized so a warning is issued. They showed me how to tell it to ignore specific programs so it is not deleted.

Win XP will always have a place in my heart.
I was running XP on VM with my Win7, but haven't taken any steps yet to install a VM on WinX yet.
Wow! that's an ultra fast boot time! Are you using an SSD?
The fastest boot time I've been able to achieve with the new WinX OS is about 63 seconds. My bios is what takes up much of the boot time, plus I'm only working with 2 cores and conventional HDD's.
I'm looking to upgrade my CPU, but can't seem to make up my mind as to what processor to upgrade too and whether to part with the cash. I also my want to replace my Mother-board as well. To make it easier to upgrade the CPU and other components in the future.

Not using an SSD and I was referring to my XP VM Wallace. Still, it only takes more then 20 seconds to get to my login screen with Win10 host from boot since they cheat (a modification to hibernate; mine was already enabled for this quick boot trick). I do, every so often, do a complete cold boot using a script (has to be run as administrator) which I included the code for you (just save it as a batch file).

Of course, when you power back up, it will take a little longer. I bought a screamer though a year ago so even on clean boot, it's well under a minute.

I always seem to be at 63 to 67 seconds. My bios is the killer of my boot time.

Just check. Including putting my pin number in, I got to the desktop and fully functional (well, HD was still thrashing; lol) in 54 seconds (cold boot); got to pin log-in screen withing 30 seconds (again, after turning off using method mentioned; it would have been under 20 seconds if I didn't do that).

Still... that's great boot time.