Jump to content

FOLBlog

Members
  • Content Count

    2
  • Joined

  • Last visited

  1. I made a registry defragmentation with Wise Registry Cleaner 7.85.516 version and the PC, after reboots, run into an endless bootloop. I tried the workaround explained here http://forum.wisecleaner.com/index.php?/topic/439-win8-entire-registry-wiped-on-defrag-782512/ but it didn't work. Could anyone suggest something else to try to solve the problem? TIA
  2. 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.
×
×
  • Create New...