Jump to content


Photo

[Win8] Entire registry wiped on defrag? (7.82.512)

RegCleaner Windows 8 Win8 defrag fatal error boot error registry

  • Please log in to reply
5 replies to this topic

#1 Sparktank

Sparktank

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 01 August 2013 - 09:06 AM

Hello, I'm a huge fan of the freeware for Reg/Disk cleaner and use it often.
My primary machine is a Windows 7 (64bit, UAC disabled, always elevated privileges).
My secondary machine is a Windows XP (32bit, always elevated privileges).
 

 

But this is regarding an issue I had after using RegCleaner on a friend's laptop and how I solved it.
This information may be useful to the developers. It's not fully intended for other users to use as a solid solution to any given problem.
I believe my problem may have been purely circumstantial and rare.

DISCLAIMERI don't claim that it will work 100% or for all situations. Please consult with a technician for precise support and advice. If you proceed to try, try at your own risk as I assume no responsibility.
 
Disclaimer #2: ...I have next to zero knowledge about Windows 8.
 
 
 
Version: 7.82.512
Settings: Deep scan, no back (never caused problems before)
 
Friend's Laptop:
Pre-configured/Pre-installed, Easyhome, Gateway, Windows 8 (64bit)
 
 

 

 
Problem:
However, I used a portable version on my friend's laptop (Windows 8, 64bit, always elevated privileges).
 
The regular scan went fine. I even looked at the "Unsafe" registry pointers and felt they were safe enough to add to the wiping process. They pointed to games no longer installed.
 
I then did a scan for the Registry Defrag process and it took only less than 2 seconds to scan.
The percentage said it could defrag up to 92%!!!
 
I hadn't cleaned his registry in a long time (using older versions) so I thought this was just accumulated over time from installing/uninstalling software/games.
I proceeded to reboot the machine and it caused a fatal error where it wouldn't load Windows.
Instead of showing his user account to sign in, it just said "Something went wrong: critical_process_died"
 
 

 

 
Symptom:
  • The laptop began an endless cycle of rebooting and terminating prior to the log in screen with the same fatal error message.
  • "Something went wrong: critical_process_died"
  • Unable to boot into "safe mode"
  • Unable to boot into "Debugging mode"
  • Unable to boot into "Logging mode"
  • Windows Restore unavailble
  • Windows Explorer could not be opened

 

 
NOTE: This boot menu may be different for other users! This is a pre-configured laptop!!!
 
 

 

Positives?

  • Command Prompt was available
  • No files were actually altered/removed
 
 

Solution:

"RegBack"
 
I took his laptop to my home (he has no internet) and googled for similar issues, starting with "registry disappeared".
I found a great deal of talk about "Regback" so I googled that next and found several recommendations that repeated multiple times.
 
I was able to change the boot options to allow me to enter the Repair/Diagnostic function.
From there I accessed the "Command Prompt" which allowed me to see that all the files were indeed still there, just that I couldn't run any program.
Since no files were deleted or anything else altered, I figured that the registry had been completely (or nearly all of it) had been wiped.
I was able to open "regedit" from the CMD in the diagnostic mode.
Sure enough, the "Software" folder for several of the main entries were missing!
 
This lead me to believe that RegCleaner misinterpreted the size it could actually defrag somehow and wiped a lot of vital information.
Including system registry entries that allowed programs to be executed, windows explorer to be opened and even for Windows OS to boot and "Safe Mode" to not boot at all.
 
So I went back to the google search results and read over the details of other people's problems and how successful they were.
Some reported to use "Windows Restore" but that was not available.
CMD was available so I looked over the "RegBack" option several times before trying it out.
 
It was completely successful!  :D 
Upon reboot, I was shown the screen to sign into his laptop and access the desktop.
Windows explorer opens, software executes properly.
Everything was 100% operational again.
 
Solution Details:
Disclaimer #3: I don't claim that it will work 100% or for all situations. Please consult with a technician for precise support and advice. If you proceed to try, try at your own risk as I assume no responsibility.
 
Although the solution was for Windows 7, it proceeded to work on Windows 8.
If you were to google about Windows 7/8 and "regback" together, you'll stumble upon the same recommendations.
 
Website (Microsoft website) with details on semi-related issues with RegBack solution.
The RegBack process: (Spoilered for size)
Spoiler

 

Summary:

I have no idea if this has happened to any Win8 users before or if it's just something from this version.

I've cleaned and defragged with Deep Scan/No Backup before and had no issues.

 

After having restored the backed up registry from Windows\System32\config, I did changed the settings in WRC.

 

New Settings:

"Show Safe Only"

"Create backup before cleaning"

 

The cleaning process goes without a hitch.

However, the scanning for defrag still shows a 92% reduction size.

 

Here's a screenshot of what WRC shows it can reduce...

Attached File  WRC_92p.png   106.25K   8 downloads

 

I'm not going to defrag it, in fear of having to do the RegBack process all over again.

 

I'm going to do several virus/malware scans to see if there's an infection of any kind.

 

Questions:

Is there any way to confirm if this is a bug in the most recent version? (7.82.51)

Would a virus/malware infection lead to WRC to wiping out an extremely large portion of the system registry?

Is there anything else I can provide to further help with the understanding of the problem?

I wouldn't know where exactly to look for pertinent logs that would better indicate the source.

 

Thank you for your time and wonderful programs.

I hope this serves useful.



#2 WiseCleaner

WiseCleaner

    Advanced Member

  • Moderators
  • 1,093 posts

Posted 02 August 2013 - 09:15 AM

Thanks for your post very much. It has been submitted to our Tech team for a further analysis and development. 


We want to put smile on your face.    :)

 

Any feature questions and ideas, please feel free to contact us!

-----

News: Halloween 2017

 

banner_activity.png

-----

Best Regards,

WiseCleaner.com

Follow us on:

 facebook.png  Twitter.png  gplus-32.png  YouTube_32x32.png  linkedin_32x32.png

 


#3 FOLBlog

FOLBlog

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 25 September 2013 - 11:21 AM

The RegBack process:
You could use this process instead:
1. Set your BIOS to use the DVD drive as the primary boot device.
2. Boot with your Windows 7 installation DVD or the Windows Repair CD.
3. Press a key when the message indicating "Press any key to boot from CD or DVD …" appears.
4. Select a language, a time and currency, and a keyboard or input method, and then click Next.
5. Click Repair your computer.
6. Select the Command Prompt.
7. Identify the correct drive letter for your Windows installation. It could be a drive other than C: but it won't be X:. You do it by typing the commands
dir C:\Win*
dir D:\Win*
dir E:\Win*
until you find the Windows folder.
I will call that drive "Q:".
8. Type these commands:
cd /d Q:\windows\System32\config
xcopy *.* Q:\RegBack\
cd RegBack
dir
9. Examine the dates of the Software, System and SAM files. Were the files created before or after your problem became apparent?
10. If they were made before the problem became apparent then you can type these commands:
copy /y software ..
copy /y System ..
copy /y Sam ..
(the two dots are part of each command)
11. Reboot normally. If things do not work out then you can backtrack by copying the original registry files from Q:\Regback to Q:\Windows\System32\config.

 

I think there are a few mistakes in this procedure.

The "xcopy *.* Q:\RegBack\" command creates a new folder in the root directory (Q:\) not in the supposed Q:\windows\System32\config folder.

The right command is xcopy *.* RegBack which asks user to create a new folder (RegBack) inside the current directory (Q:\windows\System32\config).

If you type the wrong command, commands that follow don't work.

 

It seems that the purpose of this procedure is to replace old SYSTEM, SAM and SOFTWARE files with an identical copy of themselves...weird.

It could be logical to think to replace them with an older copy of them (one of those taken before the disaster, if there are any).

I tried this procedure with a PC running Windows XP; after the registry defragmentation made by Wise Registry Cleaner (7.85.516 version), the PC run into an endless bootloop.

In C:\Windows\System32\config folder I've found an old copy of those 3 files but SYSTEM, taken a few minutes before the defragmentation, and which name ended with se suffix .bak.

I tried to restore them by replacing actual SOFTWARE and SAM file but the bootloop didn't disappear.

 

It could be very useful and very...wise, making Wise Registry Cleaner able to take a copy of those files (better of complete config folder) before defragmenting registry.



#4 wisecleaner_admin

wisecleaner_admin

    Administrator

  • Administrators
  • 2,176 posts

Posted 26 September 2013 - 10:02 AM

Hi, Sparktank

Thank you very much!!! Our tech team have modified this problem.

I send a license key of Wise Care 365 to you (in your Inbox) for your help.


  • Sparktank likes this

We want to put smile on your face.   :)

 

Any feature questions and ideas, please feel free to contact us!

-----

News: Merry Christmas. 

 

christmas-2017.png

-----

Best Regards,

WiseCleaner.com

Follow us on:

facebook.png  Twitter.png  g+32.png  YouTube_32x32.png  linkedin_32x32.png


#5 Sparktank

Sparktank

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 26 September 2013 - 11:01 AM

I think there are a few mistakes in this procedure.

 

I wouldn't know too much to confirm nor test anything.

That was a popular method on the internet, from Microsoft forums as well.

It did the job, however.

 

Hi, Sparktank

Thank you very much!!! Our tech team have modified this problem.

I send a license key of Wise Care 365 to you (in your Inbox) for your help.

 

That's wonderful news! :)

If any more issues arise in the future, I'll be sure to provide more information.

 

I still use the Disk/Reg Cleaners on a weekly basis.



#6 april

april

    Advanced Member

  • Members
  • PipPipPip
  • 927 posts

Posted 27 September 2013 - 08:44 AM

Ok, thank you so much ! :)







Also tagged with one or more of these keywords: RegCleaner, Windows 8, Win8, defrag, fatal error, boot error, registry