SOLVED Update Windows 7 Prof Cortana

[moiseyo]

After Update Windows 7 to Window 10 a few applicator behavior is not correct
One of them Cortana . I Google and ran program :

sfc /scannow

The result is not good


########### Result ----------------
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

about 800 entries like - Error - Overlap: Duplicate ownership for directory

I checked a few and found that duplicates entries are for and found


Owner :NT SERVICE\TrustedInstaller
Security entries:

Account:CREATOR OWNER ->268435456
Account:NT AUTHORITY\SYSTEM ->268435456
Account:NT AUTHORITY\SYSTEM ->Modify, Synchronize
Account:BUILTIN\Administrators ->268435456
Account:BUILTIN\Administrators ->Modify, Synchronize
Account:BUILTIN\Users ->-1610612736
Account:BUILTIN\Users ->ReadAndExecute, Synchronize
Account:NT SERVICE\TrustedInstaller ->268435456
Account:NT SERVICE\TrustedInstaller ->FullControl
Account:APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES ->ReadAndExecute, Synchronize
Account:APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES ->-1610612736

I ran command

Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like "*SystemApps*"} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

The problem did not go away


Are any tools to fix it ?

 

[Saltgrass]

Copy and paste the command line below in the Admin Command Prompt. It will place a text file on your Desktop. Open that file and look near the end of the listing. You will see comments about a file not being repairable. See what that file/s is. It only takes one file to give the error message and it may be one which is known.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

 

[moiseyo]

Copy and paste the command line below in the Admin Command Prompt. It will place a text file on your Desktop. Open that file and look near the end of the listing. You will see comments about a file not being repairable. See what that file/s is. It only takes one file to give the error message and it may be one which is known.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

The end if file


2016-07-03 14:59:02, Info CSI 000057bc [SR] Beginning Verify and Repair transaction
2016-07-03 14:59:02, Info CSI 000057be [SR] Cannot repair member file [l:20]"Windows.UI.Logon.pri" of Microsoft-Windows-UI-Logon-Library, version 10.0.10586.420, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-07-03 14:59:02, Info CSI 000057c1 [SR] Cannot repair member file [l:20]"Windows.UI.Logon.pri" of Microsoft-Windows-UI-Logon-Library, version 10.0.10586.420, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-07-03 14:59:02, Info CSI 000057c2 [SR] This component was referenced by [l:80]"Package_1280_for_KB3163018~31bf3856ad364e35~amd64~~10.0.1.2.3163018-2765_neutral"
2016-07-03 14:59:03, Info CSI 000057c5 [SR] Could not reproject corrupted file [l:47 ml:48]"\??\C:\WINDOWS\SystemResources\Windows.UI.Logon"\[l:20]"Windows.UI.Logon.pri"; source file in store is also corrupted
2016-07-03 14:59:03, Info CSI 000057c8 [SR] Repair complete
2016-07-03 14:59:03, Info CSI 000057c9 [SR] Committing transaction
2016-07-03 14:59:03, Info CSI 000057ce [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
-----------------------------------------

How I Fix/Delete those files ?

 

[Saltgrass]

The Windows.UI.Logon.pri file I would think is fairly important and appears to be related to the Logon background. Although the error does not necessarily mean the file is corrupted but may just mean the metadata which is checked does not agree. It seems a recent update is referenced concerning the file.

So the first thing I would try is to run the DSIM command to see if it can replace the file or correct the metadata. I saw a thread where another person had this situation and running DISM three times corrected the situation. If you get a message about not being able to find a source file we will have to go into specific repair operations.

So open the Admin Command prompt again and use the command below. Hopefully, it will correct the problem. If you have made any changes with your logon background, it may be involved.

DISM /online /Cleanup-Image /RestoreHealth

 

[moiseyo]

The Windows.UI.Logon.pri file I would think is fairly important and appears to be related to the Logon background. Although the error does not necessarily mean the file is corrupted but may just mean the metadata which is checked does not agree. It seems a recent update is referenced concerning the file.

So the first thing I would try is to run the DSIM command to see if it can replace the file or correct the metadata. I saw a thread where another person had this situation and running DISM three times corrected the situation. If you get a message about not being able to find a source file we will have to go into specific repair operations.

So open the Admin Command prompt again and use the command below. Hopefully, it will correct the problem. If you have made any changes with your logon background, it may be involved.

DISM /online /Cleanup-Image /RestoreHealth

I had in the same directory file Windows.UI.Logon.pri,bak
I rename it back and now scan is OK

Thank you this problem gone.

Now I have error in event log

---------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user MOISEY-PC\MOISEY SID (S-1-5-21-573147726-3479669810-588349159-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative
----------------------------------------------------------------------------------

I checked permissions in registry and all ok

 

[moiseyo]

I have found help
https://shauncassells.wordpress.com...d-d63b10c5-bb46-4990-a94f-e40b9d520160-and-a/


The case can be closed

 

[Saltgrass]

Those types of problems pop up every now and then. I have no idea what is changed causing a situation with local activation... I was never able to fix it using the Component Services until I had changed permissions elsewhere to make it possible.. Glad you found the answer.