Author Topic: Tweaking.com - Windows Repair (All in One) v1.8 killed Windows 8  (Read 8912 times)

0 Members and 1 Guest are viewing this topic.

Offline streetwolf

  • Jr. Member
  • **
  • Join Date: Aug 2012
  • Posts: 99
  • Location: New Jersey, USA
  • Karma: 1
    • View Profile
I installed WR(AIO) 1.8 on my Windows 8 Pro x64 RTM (Technet version).  I took a few disk images of my system/boot drive and figured, what the heck, let's do all the repairs. I checked the box to do a restart after WR completed it's work.  During the repairs I noticed that some things were highlighted in red and I saw some fails, as in Fail:2.  I didn't record any of the info on the screen because I knew logs were being created.

When WR was done and didn't seem like it would restart I did it myself (Maybe a mistake?).  Windows 8 came up did a little dance, made a little love, than promptly hung.  I then get a screen that tells me Windows encountered a problem and will try to fix it.  Screen just kept staring me in the face, apparently hung.  Tried rebooting and didn't even get into W8 at all.

Sure glad I made those disk images.  Did a disk image restore and I'm back in business.  Needless to say the WR logs were on the drive I just restored so I got nada, zip, zilch, bupkis to show you.

Is WR 100% compatible with W8 or did I just prove it isn't?  I took the risk of doing everything, although if only tried to repair one thing it might have be the one that caused the problem or maybe it's a combination of repairs. 

Take this report as you may.  No finger pointing on my part.  But as they say, 'Caveat Emptor'.
Intel Core [email protected] | Gigabyte Z390 AORUS MASTER | Corsair 1000W PSU | Corsair H115i CPU Cooler | Corsair 32GB RAM | EVGA GTX 1080 Ti FTW3 11GB | BenQ PD3200U 32" 4K LCD | 4-512GB Samsung 970 PRO M.2 | 2TB Samsung 860 EVO | 480GB  SanDisk USB Extreme900 | Windows 10 Pro | FIOS 1Gb

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Tweaking.com - Windows Repair (All in One) v1.8 killed Windows 8
« Reply #1 on: August 26, 2012, 02:30:16 pm »
I have installed Windows 8 RTM in vmware and ran every single repair. Everything kept working perfectly. :cheesy:

So I am wondering what is different on your machine, and exactly which repair caused the problem :wink:

If you are willing to work with me I would like to trace down what went wrong. But it will take a little work.

First I want to make sure you make or keep a good image of the OS so you can put it back when we find what went wrong :-)

The trick is to run each repair 1 at a time and reboot each time and see if we can find what repair messed up.

Let me know if your willing to help me trace it down.

Shane

Offline streetwolf

  • Jr. Member
  • **
  • Join Date: Aug 2012
  • Posts: 99
  • Location: New Jersey, USA
  • Karma: 1
    • View Profile
Re: Tweaking.com - Windows Repair (All in One) v1.8 killed Windows 8
« Reply #2 on: August 26, 2012, 03:43:58 pm »
You bet I'd like to test this out for you.  No pain no gain as they say.  The thing about any type of program that fixes or cleans your system are the bad things that might show up days or even weeks later as a result of the cleaning/fixing.  Perhaps you use a function that you normally don't use until a week after the clean/fix and it doesn't work.  First of all was it the fixer program that caused this or was it something else? At that point any backups you've made before the fix will wipe out all your changes you made to your system when you do a restore.  That in itself could be more of a headache than any errors you were trying to clean up in the first place.

Maybe you should keep your logs on another drive so at least if you have to restore an image you have the logs to see what was happening?  Since I never got a chance to look at the logs can the logs be used to reverse the changes made, or is that done via some other method?  I'm thinking along the lines of Registry Cleaners that will make a backup of the keys it deletes or changes.  This way you can do selective key restores without having to restore the entire Registry.

I have years of experience testing all kinds of software especially system utilities.  As long as I have a working Disk Image program I am covered.  But then again I've had some bad images at times that verified as good when I took them so nothing is 100% ;-)  That's why I take at least three backups to internal and external devices.  Lessens the chance of a bad image but does not guarantee all the images are good when you need them.

Also since W8 requires something like W7 to upgrade from, and because there is no clean install with the current RTM, this adds to the problem of reinstalling W8 if all else fails.  I do have a W7 image that's a few weeks old just in case but I hope it doesn't come down to using it.

It might be more convenient to communicate via email regarding my testing.  I assume you have my email address on file.  Send me your plan of attack.
« Last Edit: August 26, 2012, 03:48:05 pm by streetwolf »
Intel Core [email protected] | Gigabyte Z390 AORUS MASTER | Corsair 1000W PSU | Corsair H115i CPU Cooler | Corsair 32GB RAM | EVGA GTX 1080 Ti FTW3 11GB | BenQ PD3200U 32" 4K LCD | 4-512GB Samsung 970 PRO M.2 | 2TB Samsung 860 EVO | 480GB  SanDisk USB Extreme900 | Windows 10 Pro | FIOS 1Gb

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Tweaking.com - Windows Repair (All in One) v1.8 killed Windows 8
« Reply #3 on: August 26, 2012, 03:49:45 pm »
Sure, my email is shane at tweaking.com

The reg backups is how to restore things before the repairs. So I made sure that was in the program. Also if the system locks up again we can use the reg backup to restore the registry before the repairs. This would at least tell me if the restore of the reg fixes it means that it is a reg setting that got changed that is causing the problem.

I did a fresh install of Windows 8 RTM in vmware, nothing else installed at all and ran all the repairs. I didnt do a Win 7 to 8 upgrade.

But your the first to report a problem with 8. So this is perfect timing to find out what it was and get it fixed before Windows 8 goes live to the masses :artist:

Shane