Tweaking.com's fixer

I followed their instructions but it will not start repairs. (It does the scans.)

Since they put it in Safe Mode with Networking, I'm guessing that it needs a network connection. Yet Win10 doesn't have wifi in Safe Mode. Should I jump through the hoops needed to enable wifi, or is that a waste of time and it won't work anyway? Shouldn't their instructions mention Win10 wifi not being on, or is there some different problem going on? I'm asking here because their own forum seems not very active.

While on the subject, does anybody have opinions on whether it's good to run their repairs? I just want to do the registry, file and folder permissions. Out elsewhere in the world, some same it's great and some say it made their computer not boot. I've made a Restore Point, presumably that should handle any problems that might arise.

dalchina said:

Hi, I don't know why a connection would be needed;

That's what I'd also figured, but I just tried running it in regular (not Safe) mode, just a simple thing to restore .bat associations. And that worked.

here's what I'd do:

a. Create /update my disk image before attempting any repair. (Hopefully you are using disk imaging regularly as is endlessly recommended here e.g. Macrium Reflect).

I had made an MR7 image 2 weeks ago. I suppose I can maybe fit an update on my almost filled ext HDD.

b. Tweaking.com tells you to or creates a restore point (but restoring isn't always successful, plus less useful if your PC becomes unbootable).

oh boy

Yes, sometimes their repairs help people.

I found this on their site:


Hmm, Win 8? Guess they forgot to update the text...


If it won't actually complete or start effecting repairs, suggests something really is amiss with your O/S

Well, thanks for looking. That is considerate.

Yep, there are lots of intransigent problems from the March forced update: has anybody fixed the Cryptographic Services problem?

Summary of bad: Crypto Service, permissions, plus no updating works and no-troubleshooters work.

Just 1 example: I right-click to bring up the context menu and that might take a full minute, because CryptS hogs the HDD. That' why I think trying a repair-install or a version revert might fail. (Someone suggested a manual revert, mainly done by swapping out Windows folder and replacing with the one from Windows.old. I can do that from a live Linux, but seems risky.)

- or perhaps the disk?

Have you run a disk check (3rd party tool)?
Have you run e.g.
chkdsk c: /scan
from an admin cmd prompt?

yep, I've done those many times. Back in the simple days in mid March when I'd thought looking at CBS.log might help :)

No such problems until *immediately* after the 1909-2004 upgrade. There are lots of posts around the web about CryptoS running amok right after an update, going back over years. I did try deleting the ProtectedRoot reg key, which works for some but not for me. Deleted catroot2, the update files, everything like that over weeks.

It is a puzzler. Why does CS run amok, what does it want? Why does the builtin admin not get blocked for Device Manager et al. while the regular admin accts do get blocked, and the perms all seem as they should be and are the same as in Windows.old. I will probably disable LUA in the registry (that does work to prevent spurious UAC) before attemptig a big fix, but the CS still runs amok regardless.

No such problems over 20+ yrs with Windows, either. But yes, i will never again be forced into an update.

Edit: since onset was immediate after update, and since disabling LUA helps, I think it's not a bad disk problem since that wouldn't be labile.]

Got it done. It accomplished nothing, a waste of time.