'Warning: Overlap: Directory' recorded in my CBS.LOG file

[streetwolf]

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}

[Boggin]

I ran a sfc /scannow on this machine yesterday but my CBS log is empty.

I had run a dism /online /cleanup-image /restorehealth first though but I had also done a reset on this machine following the 1903 update, because I was unable to access Event Viewer because of a MMC error which MS has since resolved through another update.

However, following a sfc /scannow on my other Win 10 laptop, I have the same overlap warnings in its CBS log.

A Google on this reports others have found this and it has been attributed to upgrading to Win 10 from a lower version of Windows.

Both these machines were previously Win 7.

From Google I've seen it suggested to do a repair install, but unless MS have fixed this, a repair install on 1903 fails with an error code.

This was why I reset that laptop with the MMC error.

A reset is also suggested as a fix for this overlap, although I don't know of any adverse effects caused by this overlap.

I noticed my version of Win 10 is .239 whereas yours is .267

On checking for updates they are both now in the process of installing KB4505903 which may bring them up to .267

I may get around to resetting my other laptop this week, but as it's my secondary machine, that isn't a priority but I think the only fix for this would be a reset, unless the dism /restorehealth cmd had some effect in resolving the overlap problem.

You could try that cmd followed by another sfc /scannow to see if the CBS log still has those warnings.

While the reset retained my personal stuff, I had to reinstall my previously installed programs but didn't bother with a lot of the Toshiba pre-installed utilities.

[Boggin]

Scrap that idea of a reset.

Following that update installation I performed another sfc /scannow on this machine and the CBS log has the same overlap warning.

I haven't noticed any adverse effects on this machine, so I guess it's just something to live with.

I have no intention of performing a clean install to see if it resolves, even after creating a system image to restore with.

[streetwolf]

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

[Boggin]

Well I wouldn't have known about it if you hadn't queried it.

It isn't the only thing that was duplicated during the upgrade.

The Win 7 Recovery partition is still there in addition to the one created by Win 10 - in fact I have two created by Win 10 of slightly different sizes.

[streetwolf]

I've had this happen in the past and I used partitioning software to get rid of the rightmost one. No need for two.

[Boggin]

I'll just leave things as they are - it doesn't cause any problems.