Main Forum > Feedback & Suggestions

What Have You Done to My Machine?!?!

(1/2) > >>

wmcole:
I ran Tweaking to repair a system which sfc and standard dism, chkdsk etc found no problems with but which kept randomly rebooting of turning off all output to the monitor.  Now, I can't set default programs, (among other settings that I can no longer change either in the new Windows 10 settings or traditional control panel - I click a choice but nothing happens, and my choices are ignored.  It appears you somehow set permissions to all these settings so that I, as Administrator cannot set them.

Further, the advent of a random restarts / black screens comes quicker and in larger number after the so-called "repair".

I'd love to look at the event log, services app, dcomcnfig etc. but attempting to run any of those apps crashes the machine almost immediately.  And yes, I started from step on, and did all the optional steps before repair.  What a wast of 6 hours.

BTW, I tried to restore both the registry and to the restore point I created before I ran this sorry utility, and guess what - THE SYSTEM TELLS ME THERE ARE NO BACKUPS OR RESTORE POINTS TO USE TO GET BACK TO WHERE I WAS BEFORE THIS PIECE OF POOP SCRAMBLED MY OS!!

Thanks!  Now I have no choice but to wipe the HD and start rebuilding from scratch - a process that will likely take two months to complete.

 

Boggin:
Hang slack on that - I've emailed Shane with a link to your thread and any problems with WR grabs his attention.

Shane:
My program didnt do that to your system. Random reboots and black screen normally means you have a hardware problem. The program also did a registry backup which you can restore.

When you did the chkdsk on the drive did you do just the normal one or did you do the one to have it check for bad sectors?

The thing that happens if a person has bad sectors on their drive is when permissions are set or files are registered (writing to the registry) and pretty much everything the repairs touch make windows write to the drive, the registry is a database file and so you write anything to it and the drive is written to. So where nothing was on a bad sector after the repairs and all the new drive writes something can end up on a bad sector and then you see all hell break lose.

Shane

wmcole:
The program DID NOT do either a registry backup or create a restore point in response to selecting those buttons on one of the tabs.  When I clicked them the UI flashed and that was it.  I thought, "wow, that's fast."  But after the scrambling (aka "repair") step, when I went to use the restore point, I got the system panel that told me there were NO restore points to restore to.  This includes the one I made myself right before running Tweaking.com - Windows Repair.  Then I tried the restore registry button - guess what - no saved registry to restore from.

So I went manually searching for where you might have saved the backed up registry.  Couldn't find it anywhere.  So, no, your program did neither such thing except perhaps to some temporary / imaginary location that ceases to exist as soon as the scambling (aka "repair") has been "accomplished".  And there is no record of them having been made in any of the log files left behind after I uninstalled this ..... GRRRrrr!

(Log files attached).

Boggin:
You've run the chkdsk in read-only mode which can falsely report errors if it's being written to at the time.

In the first chkdsk log it does report errors and that it cannot continue.

Run the chkdsk again but as chkdsk /r

This will repair any file corruption and if it finds bad sectors, will move what data it can from there to good sectors while roping those sectors off so that nothing can be written to them.

Navigation

[0] Message Index

[#] Next page