Main Forum > Tweaking.com Support & Help

Registry Compressor bug in XP

(1/6) > >>

neroilo:
SYSTEM and NTUSER.DAT Registry hives were not compressed in my XP SP3 Pro, even in safe mode, using the best compression option.

I have some compressed hives named as SYSTEM.NEW and NTUSER.DAT.NEW.

Shane:
If the system had trouble with SYSTEM.NEW then the ntuser.dat wouldn't be replaced either.

Here is how the program works.

1. It saves each registry hive to a new file and adds .NEW to those files. (it does this on Step 1)
2. When you click step 2, it tells windows to start using the .New file and to rename the current ones to .OLD
3. So at reboot only the .OLD files should be left. In order to replace the ntuser.dat I have to use the pending rename operations. Which has to be loaded in the system hive. So since the system hive didnt get restored to the new file the ntuser one didnt either.

So the question is why didnt the system.new take?

I dont have any error reporting in the program, I may need to add some.

Go ahead and delete the .new and .old files and try again and let me know how it goes. :wink:

Shane

neroilo:

--- Quote from: Shane on March 28, 2013, 04:32:33 pm ---
Go ahead and delete the .new and .old files and try again and let me know how it goes. :wink:


--- End quote ---

I already did it, but it doesn't work either.

Shane:
I will have to put some error reporting into the program so we can see why it isnt taking the new system hive then :-)

Does it work if you try the other compression options?

Shane

neroilo:

--- Quote from: Shane on March 28, 2013, 06:34:46 pm ---Does it work if you try the other compression options?

--- End quote ---

No, it doesn't, even after deleting .old and .new files.

This issue regards all compression options.

I have Panda cloud antivirus free in the background + Windows Firewall + Process lasso Pro edition (last stable version with default settings, no changes).

Navigation

[0] Message Index

[#] Next page