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.


Topics - streetwolf

Pages: [1]
1
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}

2
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:

3
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.

4
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.

5
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:

6
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}"


7
Just installed the update and now clicking on any of the tabs does nothing.  I always remain at the Backup Registry menu.

8
Since upgrading to v2.0 I can't get RB to run via the task scheduler.  Running it on demand indicates it worked but the backup is no where to be found.  However,  I can run a backup within the program itself and it is placed where I specify.  Any ideas Shane?

9
Doesn't  add anything to the right-click context menu.  Running Windows 8.1 Pro x64.

10
I'm running Windows 8.1 Pro x64 RTM.  I get the message below whenever I fire up RB.  Can you add 8.1?  I use the 7/8 VSS and it works fine.

---------------------------
Tweaking.com - Registry Backup
---------------------------
Unable to detect which version of Windows to run the VSS. Please manually select the correct VSS exe to use.
---------------------------
OK   
---------------------------

Just noticed something else.  Each time I take a backup using VSS I get the following error in my Event Log.  It appears in pairs and looks like one is when the backup starts and the other one when it ends.  This is based on the times of the two events.

Event 513, CAPI2

Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.

System Error:
Access is denied.

Here's a little info on the error: Event ID 513 — Shadow Copy System Writer Functionality  I checked the stuff listed and all is as it should be.  System Write is also active:

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {b5ea371d-21d4-49d4-bf12-fa83ea49365d}
   State: [1] Stable
   Last error: No error

I've also attached the Log_Vss.txt file

11
I did a clean install of Windows 8 Pro x64 due to some nits.  After I installed all the available Window updates I ran Disk Cleanup to delete them.  There was about 1GB of stuff that got deleted.  However, I can't seem to delete 28.0 MB of Windows updates as reported by Disk Cleanup.  It always stays at 28.0 MB after every attempt to clean them.  I tried a couple of things to try and fix it without success.

1. Deleted the SoftwareDistribution Folder and rebooted which is worse then the 28.0 MB.  I had backups :-)
2. Ran Dism /Online /Cleanup-Image /RestoreHealth.

Any ideas on how to get this down to 0 bytes?  I've seen it this way after past installs.

12
After I did a clean install of Windows 8 Pro X64 under a UEFI environment and formatting my boot/system drive as GPT I always get a message after RB runs as an auto backup, when I first start up my machine, stating that an error was encountered.  Examining my backup folder it appears everything was backed up. I do not get any error message if I run RB manually.  Prior to converting to UEFI I had no problems.

Here's what I have in the Event Log:

Faulting application name: TweakingRegistryBackup.exe, version: 1.4.0.3, time stamp: 0x5071e5f1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x770
Faulting application start time: 0x01cdd6d791f65069
Faulting application path: C:\Program Files (x86)\Tweaking.com\Registry Backup\TweakingRegistryBackup.exe
Faulting module path: unknown
Report Id: d90fd982-42ca-11e2-bed1-c86000a0a026
Faulting package full name:
Faulting package-relative application ID:

13
Tweaking.com Support & Help / Registry Backup 1.4.1
« on: September 14, 2012, 06:07:46 am »
Circled in red some truncated text.  Probably because I use 120 DPI.

14
Feedback & Suggestions / One man's opinion on cleaners and fix it programs
« on: September 04, 2012, 09:03:22 am »
1. If the cleaner/fix it program is supplied by the software/hardware manufacturer to correct problems than I have no problem with it.  They know what their program does and how to fix it.  OK.... maybe not Symantec  :wink:

2. Regarding your general cleaner/fix it programs.  In many cases the cleaner/fix it developers have no idea what a given program's reason is for doing something.  In most cases this involves Registry entries.  A developer can decide to use a non-existent file name to set an option or keep track of something, it's entirely up to him/her.  Along comes your Registry Cleaner and bam it deletes this entry because the file does not exist on your disk.  Result.... the program doesn't function as it should, if at all.  I see a lot of entries in the Registry that look like file names but upon close inspection are clearly used for some other purpose. 

3. All cleaner/fix it programs should show the user what it is about to do and let the user decide whether to continue.  This in conjunction with saving backups of anything that is about to be changed, whether it's files or Registry entries.  A full Registry backup is not enough. If you ever need to use it to fix a problem, well after the fact, you will lose any new entries.

4. Only use documented methods to clean/fix.  The developer's assumptions about the way things should be cleaned/fixed can lead to disaster.

5. Caveat Emptor was never more applicable than with cleaner/fix it programs.

6. Only use them if you absolutely must and realize the possible consequences.  Once burned, twice shy.

Stepping off soapbox......

15
I installed WR(AIO) 1.8 on my Windows 8 Pro x64 RTM (Technet version).  I took a few disk images of my system/boot drive and figured, what the heck, let's do all the repairs. I checked the box to do a restart after WR completed it's work.  During the repairs I noticed that some things were highlighted in red and I saw some fails, as in Fail:2.  I didn't record any of the info on the screen because I knew logs were being created.

When WR was done and didn't seem like it would restart I did it myself (Maybe a mistake?).  Windows 8 came up did a little dance, made a little love, than promptly hung.  I then get a screen that tells me Windows encountered a problem and will try to fix it.  Screen just kept staring me in the face, apparently hung.  Tried rebooting and didn't even get into W8 at all.

Sure glad I made those disk images.  Did a disk image restore and I'm back in business.  Needless to say the WR logs were on the drive I just restored so I got nada, zip, zilch, bupkis to show you.

Is WR 100% compatible with W8 or did I just prove it isn't?  I took the risk of doing everything, although if only tried to repair one thing it might have be the one that caused the problem or maybe it's a combination of repairs. 

Take this report as you may.  No finger pointing on my part.  But as they say, 'Caveat Emptor'.

16
I've been a long time user of the fabulous Registry Backup program knows as ERUNT.  I'm sure you know about it.  Unfortunately it doesn't work under Windows 8 and hasn't even been updated in years although it worked up to Windows 7.  ERUNT had some features that I wish RB had and maybe it does but I'm not familiar with how to use them.  They concern scheduling of backups.

1. ERUNT had a command line form that after doing the first backup of the day it would not take anymore backups if Windows was restarted.  I haven't come across any option like this in RB.  Every restart of Windows kicks off another backup.  Since I restart my machine and Windows very often I don't need all these subsequent backups. A backup when I first start my computer under Windows 8 is all I need.  I usually keep them for 7 days in which the oldest backup will get deleted to make way for the new one.

2. ERUNT had a silent mode where the backup took place site unseen. No message boxes, no status bars, no anything.  I had the option of producing messages if I wanted to.  the only message I let be displayed is any type of backup failure.

Other than these two things, RB is a fine replacement for ERUNT.

Pages: [1]