dencorso

I cannot. Last time I tried (but that was still last year) it worked OK. It was a XP Pro FPP. This year, I haven't had the need to activate any machine yet, so I cannot say.

Be careful, and hope for the best. What else?

It really has no end, isn't it? For those of you who use/have Silverlight, it was updated, too. See the MS Silverlight Release History... It all boils dow to: uninstall the previous version (probably v. 5.1.30514.0, if not earlier), because the newest installer won't do it for you, and then install the latest Silverlight (KB3056819, which has v. 5.1.40416.0). BTW, you may also find the Silverlight Balls Animation Test useful, just as I do.

Good passwords should never be shared. But if one must give it to a member one's work IT personnel, the best way out is to change the password first, then give the throwaway password created for the occasion, then change it back, as soon as possible. My 2¢ only, of course.

Something Microsoft gives one for free.

Yes. Try to activate by phone. It's automated and just works.

True. See KB896458. You might install "XP Mode" to go around it, though.

Like this one?

atmzzrSystemCheck. 'Nuff said!

Welcome back! Peace and long life!

True. And thanks for the heads up! Now, just to be fair to everyone, when Bersaglio posted, two days ago, he hadn't released it yet. I know, because I checked just after initially reading Bersaglio's post. That said, BlackWingCat does rock! And deserves lots of thanks, of course!

Ditto!

The one containing oleaut32.dll v. 5.1.2600.6688, you mean? Yes, on three different machines, since Feb. 22, and it gave me no issue whatsoever. Sure. Thank you. I didn't forget you... sorry for my silence. ATM, I'm just out of ideas.

Pale Moon for Atom will probably go on further than Pale Moon for XP... So I don't really envisage that as a very near problem. I, for one, intend to resist as far as feasible (IMO, of course)...

No. XP doesn't work well with Haswells (and Broadwells). Intel dropped XP support as of the Panther Point chipsets (B75-Z77), so that's where driver availability problems begin. There's no support for on-chip graphics nor for intel USB 3.0 since x7x, so you're mistaken about driver availability. AFAICS, i7 4930K or 4960X should also work, but nobody, AFAIK, ever tested either.

Try running: runassystem64.exe "runfromtoken64.exe trustedinstaller.exe 1 cmd.exe" to open a DOS Box as the Trusted Installer, and then run the batch from that DOS Box. This, if anything, may work.

I guess so.

Sure. Done!

Please bear with me. You had used: but ou should have used: runassystem64.exe "runfromtoken64.exe trustedinstaller.exe 1 ntregopt.exe" or a necessary parameter is missing... joakim's own example is quoted below: Have you fixed that and it still isn't working?

With all due respect, Dave, there's a long way between what is and what appears to be... Rest assured MS did much more than just that, and the fact that it isn't at all apparent isn't really that reassuring, IMHO.

Have you got it working, after all?

'Nuff said!

I use paid AVG: 2011 on 3 machines and 9.0 on one machine (an Asus EeePC 900). I've no experience whatsoever with Avast. BTW, you forgot to answer w2k4eva's question below:

If chkdsk /f finds something, I'd really start to get worried... but even if it finds anything, it cannot recreate a good profile from a damaged one. However, that's another thing you should do only after you have a good backup. Your plan to put in another disk and restore the backup on it, then work on the new disk is sound and safe. Don't try to get a shortcut... usually that's something one regrets afterwards. This is the sort of situation where Murphy's Law applies: so, one has to make sure nothing relevant may go wrong, and then nothing at all will. BTW, is your XP installed on NTFS or on FT-32? I have assumed it's on NTFS, but the only way to be sure is by asking you, of course.

My pleasure! But do keep us posted: this thread is serving as a meeting point where we exchange info on what's happening, all the time. Whenever an issue occurs, it's posted here, and so are solutions and workarounds.