Author Topic: Registry compressor problem  (Read 1787 times)

0 Members and 1 Guest are viewing this topic.

Offline Peter Pan

  • Newbie
  • *
  • Join Date: Oct 2016
  • Posts: 5
  • Location: Bulgaria
  • Karma: 0
  • Keep up smiling :)
    • View Profile
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 :)
« Last Edit: October 16, 2016, 04:07:21 PM by Peter Pan »

Offline Peter Pan

  • Newbie
  • *
  • Join Date: Oct 2016
  • Posts: 5
  • Location: Bulgaria
  • Karma: 0
  • Keep up smiling :)
    • View Profile
Re: Registry compressor problem
« Reply #1 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.
 :omg:

Offline Shane

  • Top Geek, err uh Dog.
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9274
  • Location: USA
  • Karma: 135
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: Registry compressor problem
« Reply #2 on: October 24, 2016, 11:13:36 AM »
The registry is a database file. So to clean it up the program calls the Windows API to save the registry to a new file. Thats it, nothing else.

The registry is written to a new file by Windows itself, you restart and it starts using that file. The API call is the RegSave command.

My program itself doesnt touch the registry files, so this is a bug in the Windows API itself in 10. Which doesn't surprise me as I have a seen this happen with a ton of other APi calls as well. MS is changing so many things in Windows and without any kind of error handling that they are breaking their own API calls.

What version of 10 are you using, is it the latest build?

Shane
PLEASE EDIT YOUR TOPIC AND PUT (SOLVED) IF YOU ARE ALL FIXED.

(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

Offline Peter Pan

  • Newbie
  • *
  • Join Date: Oct 2016
  • Posts: 5
  • Location: Bulgaria
  • Karma: 0
  • Keep up smiling :)
    • View Profile
Re: Registry compressor problem
« Reply #3 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! :smiley:

Offline Shane

  • Top Geek, err uh Dog.
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9274
  • Location: USA
  • Karma: 135
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: Registry compressor problem
« Reply #4 on: October 25, 2016, 12:04:27 PM »
I wonder if it is the permissions on the new files.

In my registry backup program when restoring the registry windows gave the reg files different permissions for some reason. So I had to have the permissions of the files backed up as well and I have my program apply those permissions to the new reg files.

I wonder if I need to update the reg compressor to do the same.

So as a test check the file permissions of the registry files before and after and see if they are different. If they are then restoring the permissions to what they where before hand may be the fix I need to add :-)

Shane
PLEASE EDIT YOUR TOPIC AND PUT (SOLVED) IF YOU ARE ALL FIXED.

(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

Offline Peter Pan

  • Newbie
  • *
  • Join Date: Oct 2016
  • Posts: 5
  • Location: Bulgaria
  • Karma: 0
  • Keep up smiling :)
    • View Profile
Re: Registry compressor problem
« Reply #5 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.

 

anything