Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - streetwolf

Pages: [1] 2 3 4
1
I've had this happen in the past and I used partitioning software to get rid of the rightmost one. No need for two.

2
I'll take your advice and ignore it.  Guess some past Windows update might have introduced what seems to be a bug.

3
The warnings are below.  When I run sfc /scannow no errors are reported.  When I look inside CBS.LOG I find the warning messages.  True, no errors were found but I'm curious as to the warning messages as they are always the same Directories.  I checked their permissions and nothing out of the ordinary pops out at me.  I was wondering if Windows Repair Pro AIO (latest version) might be able to fix these warnings by fixing the permissions. 

2019-07-27 16:43:51, Info                  CSI    000001cc Warning: Overlap: Directory \??\C:\Program Files (x86)\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.267, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.267, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2019-07-27 16:43:51, Info                  CSI    000001cd Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.267, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.267, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2019-07-27 16:43:51, Info                  CSI    000001ce Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.267, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.267, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2019-07-27 16:43:51, Info                  CSI    000001cf Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.267, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.267, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

4
Understood

6
The Scheduled task is set to take a backup the first time I start my machine and no more until the next day.  The compressions I've done were after this backup.  I'm sure the backup job runs just to see if it needs to take a backup.  This might be a problem.  I'll disable the scheduled task before I do another compression and see what happens.

BTW.... How come Shane doesn't seem too involved in this forum like in the old days?   Surely he has the definitive answer to all problems relating to his programs.

7
It appears so.  The error happens when Wndows starts up after a compress.

8
I do have your Tweaking.com - Registry Backup in Scheduled Tasks.  Could there be a conflict between the two?  The backup program isn't taking any backups during the times I run the Compressor.  I only take one backup a day when I first power up my machine.

9
It's not on any run list.  I run it on demand.  I didn't install it.  I guess I used a portable version.

I was indeed using the portable version.  I installed the install version and still get the same error.

10
Tweaking.com Support & Help / Registry Compressor Event Log Error 1000
« on: March 22, 2017, 07:48:02 am »
After restarting Windows 10 Pro x86-64 I always see this in my event log.  I don't get any error message other than this one.  Is there a fix for this?

Faulting application name: RegistryCompressor.exe, version: 1.1.0.0, time stamp: 0x57d82eb4
Faulting module name: MSVBVM60.DLL, version: 6.0.98.15, time stamp: 0x49b01fc3
Exception code: 0xc0000005
Fault offset: 0x00108527
Faulting process id: 0x1930
Faulting application start time: 0x01d2a31a7117c450
Faulting application path: C:\Users\garys\My Programs\Registry Compressor\RegistryCompressor.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVBVM60.DLL
Report Id: b23d5c2c-d508-4085-96ac-83dfc677a4c0
Faulting package full name:
Faulting package-relative application ID:

11
Tweaking.com Support & Help / Why has Shane forsaken us?
« on: July 09, 2016, 09:48:11 am »
Where in the world is Shane?  I haven't seen a post from him in a while.  I have a couple of problems posted that I think he's only capable of fixing, if it all.  If there are personal issues going on and he can't post at the moment I fully understand.

12
Tweaking.com Support & Help / Re: ManageACL_64.exe fault
« on: July 08, 2016, 05:05:41 am »
It seems that when I do a Registry Backup it changes the permissions of my hives.  As I stated above Windows Repair appeared to fix the permissions but RB changes them.

btw... support is sorely lacking.  Perhaps everyone is on summer vacation  :wink:.  Does Shane get involved with support anymore?  I just purchased Windows Repair Pro.

13
Tweaking.com Support & Help / Send To email problems.
« on: July 07, 2016, 08:15:20 am »
Email Recipient doesn't show up in the SendTo context menu when I right click on a file for example.  It does appear in my SendTo folder as "C:\Users\garys\AppData\Roaming\Microsoft\Windows\SendTo\Mail Recipient.MAPIMail" which from what I gathered from reading on the web is correct.  Still it never shows up in the SendTo context menu.

After running Windows Repair (all the options) it now appears in the context menu as 'Mail Recipient'.  The SendTo folder has a file called 'Mail Recipient' type is Mail Service (.MAPIMail).  Even though it now appears on my SendTo context menu opening a file with it does not do anything.  Btw.. my email client is Mozilla Thunderbird which is set up as my email client.

1. Any thoughts on this?

2. What option in Windows Repair 'fixed' this problem?  It seems the SendTo entry changes back to Mail Recipient.MAPIMail on occasion.  I'd like to be able to run just the option that affects sendTo instead of running all the repairs.

14
Tweaking.com Support & Help / Re: ManageACL_64.exe fault
« on: July 07, 2016, 08:04:03 am »
I ran Windows Repair it it seems to have restored the proper permissions to my Registry Hives.  I'll know for sure if this fixed my problem when I do Registry restore.

15
Tweaking.com Support & Help / Re: ManageACL_64.exe fault
« on: June 29, 2016, 10:50:28 am »
okay I was talking to Shane he said after you did a restore from a backup check your security tab on your registry hive if manage acl is crashing when restoring all it does is change the permissions on the registry hive files themselves when restoring make sure those permissions are correct the file locations are C:\Windows\System32\config.

I fired up a bare bones Windows 10 under a VM and their are differences in permissions.  On my 'real' system I get a message I need read permission for some of the hives.  Is their a script that can set the hives permissions back to what they should be?

16
Tweaking.com Support & Help / Re: ManageACL_64.exe fault
« on: June 26, 2016, 01:12:17 pm »
I really could use some help with my problem.  :sad:

17
Tweaking.com Support & Help / Re: ManageACL_64.exe fault
« on: June 22, 2016, 01:49:36 pm »
Is Shane around?

18
Tweaking.com Support & Help / Re: ManageACL_64.exe fault
« on: June 21, 2016, 11:31:50 am »
Is there a utility that could detect bad keys?  Perhaps the Restore has a debug mode that would list these when run?

19
Tweaking.com Support & Help / Re: ManageACL_64.exe fault
« on: June 20, 2016, 07:30:04 am »
Anyone home?  :smiley:

20
Tweaking.com Support & Help / ManageACL_64.exe fault
« on: June 18, 2016, 06:31:02 pm »
After doing a restore of my registry I always get the following error in my event log.  Do you think the restore is OK even though I got this error?  Running Windows 10 x86-64 Pro TH2.  Backup used VSS.   Used Registry Backup v3.4.1.

----------------------------

Faulting application name: ManageACL_64.exe, version: 1.2.0.0, time stamp: 0x56336288
Faulting module name: ManageACL_64.exe, version: 1.2.0.0, time stamp: 0x56336288
Exception code: 0xc0000409
Fault offset: 0x0000000000043478
Faulting process id: 0x9d4
Faulting application start time: 0x01d1c9c95603f781
Faulting application path: C:\Program Files (x86)\Registry Backup\files\ManageACL_64.exe
Faulting module path: C:\Program Files (x86)\Registry Backup\files\ManageACL_64.exe
Report Id: dd829e37-894e-4962-9afd-f9a2be1dba2a
Faulting package full name:
Faulting package-relative application ID:

21
Nothing on this?

22
Tweaking.com Support & Help / Re: Bug in Registry Backup v3.40
« on: March 24, 2016, 02:11:19 pm »
Another bug.  I no longer get the message about how many hives or whatever were backed up.  Used to say 14 of 14. Now there is nothing.

23
Hi Shane.

I use StorageCraft's disk imaging software called StorageProtect Desktop.  It comes with it's own VSS Provider.   Below are my Registry entries for the VSS Providers.  I also attached a zip file of the logs created after I ran a Registry Backup.  Can you tell from your logs which Provider I am using, MSS VSS or STC VSS?

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{24602736-bed9-4619-91b0-243447c6409c}]
@="StorageCraft Volume Snapshot Software Provider"
"Type"=dword:00000002
"Version"="1.0.0.0"
"VersionId"="{00000001-0000-0000-0000-000000000001}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{24602736-bed9-4619-91b0-243447c6409c}\CLSID]
@="{e4eb5095-f587-4159-a1d8-2710692fd243}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}]
@="Microsoft Software Shadow Copy provider 1.0"
"Type"=dword:00000001
"Version"="1.0.0.7"
"VersionId"="{00000001-0000-0000-0007-000000000001}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}\CLSID]
@="{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}"


24
It looks like it is a issue on windows 10 shane is fixing this in 3.3 it should be released tommorrow i believe  :wink:

Yeah he emailed 3.3 but it still had problems.  I mentioned those problems to him.

25
Tweaking.com Support & Help / Re: Problem with Registry Backup v3.2.3
« on: October 07, 2015, 12:17:34 pm »
Haven't posted a problem here in a long time.  I remember Shane would always reply within hours if not minutes.  Is he out of town?

Pages: [1] 2 3 4