Messages

1

Tweaking.com Support & Help / Registry compressor problem 2

« on: December 14, 2016, 09:49:37 am »

This Reply is following the locked topic:
http://www.tweaking.com/forums/index.php/topic,4921.0.html

Dear Shane,
I value very much your Registry compressor (RC), as it is the only tool in net (and I have searched and tried a lot) which is so clean and straightforward and professional! That is why I would very much celebrate it if it could be corrected to work again
I tried RC with all last WIN 10 updates, unfortunately every time it shows errors (as described in my first post) after running it, contrary to other compressors, which work without problems.

I invested a lot of time compressing the registry with RC one way and another, checking the result and reverting back to a previously saved disk backup in order to find the reason for the errors (actually always using the portable version and never having used the installable). Unfortunately I could not see where the problem comes from.

Herein I am attaching 2 text files, which I get as a result of the "DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH" command described in my first post: the first is the file showing all errors after the compression, the second one is the result on the same system but without the errors (as there is no registry compression with RC).

I hoped this files could give some clue what is happening wrong...

N.B. The command SFC /SCANNOW is NOT showing any problems!

I would be happy to help if I can in some way... 

2

Tweaking.com Support & Help / Re: Registry compressor problem

« on: October 26, 2016, 01:40:56 am »

Dear Shane,

Checked the permission before and after compression - they do NOT differ. Herein I show them:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\hivelist
ADMINS - FULL, READ
SYSTEM - FULL, READ
REASTRICTED - READ
ALL APLICATIONS - READ
EVERTONE - READ

Windows\ServiceProfiles\LocalService\NTUSER.DAT
SYSTEM - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
LOCAL SERVICE - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
USER - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
ADMIN - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)

Windows\ServiceProfiles\NetworkService\NTUSER.DAT
SYSTEM - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
LOCAL SERVICE - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
USER - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
ADMIN - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)

Users\....\ntuser.dat
SYSTEM - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
USER - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
ADMIN - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)

Users\Assi\AppData\Local\Microsoft\Windows\UsrClass.dat
SYSTEM - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
USER - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)
ADMIN - FULL, MODIFY, READ & EXECUTE, READ, WRITE (OWNER ADMINISTRATOR)

If I can do anything else please let me know,
Thanking you.

3

Tweaking.com Support & Help / Re: Registry compressor problem

« on: October 25, 2016, 06:27:35 am »

Thank you for the answer.
I myself think, that the problem is not linked with the compression of the registry, but with its saving and activating the compressed one. I have been using the registry compressor for a long time, I have Win 10 Enterprise x64, the problem started after updating Win 10 to 14393.222 (kb3194496). Now I have 14393.321 - again with the same situation, either with Fast start enabled or disabled. As already mentioned other compressors do not show this error (which means there is a solution), but they tend to compromise the registry in other ways and I personally prefer Tweaking.com Registry compressor.
If you find a way to circumvent windows API it will e a perfect solution!
Thanking you for the great work!

4

Tweaking.com Support & Help / Re: Registry compressor problem

« on: October 16, 2016, 04:10:05 pm »

I am a bit disappointed that there has been no reaction from the devs.
I tried the same situation and compressed the registry with other software and did not experience the described problem. So I am sure it is a problem of the current software.
 

5

Tweaking.com Support & Help / Registry compressor problem

« on: October 06, 2016, 06:44:29 am »

Dear Support team,

I am using regularly the Registry Compessor.

After updating Win 10 to 14393.222 (kb3194496) x64 I noticed the following error:
- after compressing the registry (option Best, Restart) and restarting the PC the command (in Command Prompt with administrator privileges): "DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH"
finishes with the error:
"The remote procedure call failed", with error No 1726.

I have repeated this several times reinstalling a working copy of my System Disk, and every time it happens again - so I am sure the compression somehow compromises the DISM command.

FYI - I am using the DISM command through the Health package (16.07.06):
https://toolslib.net/downloads/viewdownload/248-image-health/
FYI2 - It is the same situation if I use Portable or Installer version of Registry Compressor (Normal or Best compression).

Hoping to have some solution to the problem