Windows 10: Start menu - Ownership related ?

Hi guys,

Thank you for letting me join up *Smile

I have related a Start-menu+App-store problem to taking over ownership via my Admin-profile. I simply cancels out both Notification-area, Start Menu, Logging in to my account (Microsoft).

Actions taken = Locate Desktop.ini - reset values to hidden, read-only. Powershell restores (in every possible way) - and every known automated troubleshooters for Noobs.

A full reset have and will give access to menus - but I have isolated the magical disappearance to taking over ownership which at install is TrustedInstaller. I attached a debugger but after 8 pages of 0 results I'm at a loss.

YES I can reinstall - but the nerd within wants to find the holy grail. I have not located all libraries that need to be "set-back" or as the Desktop.INI (x2) set back to read-only, Hidden.

I ask for your help that does not apply to every known Powershell feature already listed for Start Menu, Reset App Store or Desktop.INI as these options won't work.

Thanks *Smile

:)

 

Temp files inaccessible on windows 10 since Oct 28 2016 update

Search in the Windows.old folder if one exists. If you have a permissions-related issue then make sure she's using an admin account and try taking ownership of the files/folders

with this.

 

Change from local account to Microsoft account permission issues

So this fixed the file write permissions in my own user folder, but it still does not fix the start menu issue, as most programs adding a shortcut to the start menu add it to the "All Users" start menu, which I'm still denied access too. I have even tried
taking ownership of the "All Users" folder, and the "All Users/Start Menu" folder. Even with ownership, I cannot change the permissions.

This is absolutely ridiculous by the way. This should not have happened at all.

 

Hello, I'm finding it a bit difficult to identify what the problem is, and what you've done - here's my attempt at interpretation.

1. I think you had some problem with the Start Menu and some apps.
2. I think you tried to solve it by taking ownership and this caused further problems.
3. You've tried certain other steps
4. Things are broken and you need help.

I can't hold out much hope for you with your current situation. Even if it appears to be working, there would be a very good chance of some other problems appearing.

I'm assuming you don't have any useful disk images- disk imaging periodically updated and on major change is about the best way of solving your own problems without technical help, saving your PC and your sanity.

I read a very very similar thread recently, where the user was recommended to reinstall.

That's what I recommend- a clean install.

Your first priority now is to ensure you have backups of all your data from favourites to videos - emails if you use an email client. Any key settings, passwords, licenses...

When you have done that, you can try downloading
Tweaking.com's repair tool (free). Use this as cautiously as it recommends.
Select only permission related repairs, preferably choosing what you think most relevant.

If that shows some promise, then I would do an in-place upgrade repair install. (Which takes about the same time as installing Windows).

Here are my notes on that.
Precede it with this in case sthg has happened to your file system:

Windows key + X, click command prompt (admin)
chkdsk C: /F
Your PC will need to restart.
Make sure the result is clear or fixed.
Post back the result, which will be on the screen briefly.
Otherwise you can get the result as follows:
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!

An In-place upgrade repair install will fix many things, but not those where the settings are not changed by the procedure.

For this you need an installation medium with the same base build as you have installed.

Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums

This will refresh Windows, after the manner of a Windows installation.
- all/most associations will be unchanged
- all your programs will be left installed
- you will lose any custom fonts
- you will lose any customised system icons
- you may need to re-establish your Wi-Fi connection
- you will need to redo Windows updates subsequent to the build you have used for the repair install
- Windows.old will be created
- system restore will be turned off- you should turn it on again and I recommend you manually schedule a daily restore point.
- you will need to redo any language downloads including the display language if you changed that)
- inactive title bar colouring (if used) will be reset to default
- if Qttabbar is installed, you need to re-enable it in explorer (Options, check Qttabbar)
This is one of the better features of Win10: as each major build comes out, that's your updated reference build, and as updates are mostly cumulative, there will be few to do.

Recommendation:
Before you perform this major repair procedure, do create a disk image.

Please consider using disk imaging regularly. It's a brilliant way to
- preserve your system (and your sanity)
- back up your data
- restore your system to a previously working state in a relatively short time

Recommended: Macrium Reflect (free/commercial) + boot disk/device + large enough external storage medium.

 

Hi and thank you so much for taking the time to answer this.

I was vague in regards to describing problems vs. solutions (actions taken).

1) Clean install of Windows 10 (Everything working)
2) Removed all unwanted software in Windows via Powershell (Startmenu + Notification area working)
3) Changed permissions = Notification+Start menu disappears

Actions taken :
1) DISM/Online /Cleanup-Image /RestoreHealth
2) SFC / scannow (Windows did not find any integrity violations)
3) Reinstall APPS via Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
4) Created New Account
5) Changed Desktop.ini back to original conf. Read-only+Hidden

No change/results

I have overlooked files or folders that need to be changed back OR I have created the problem by changing permssions in all 3 namely
Permissions, Auditing and Effective Access.

I could very easily just re-install - but it negates getting to the source of the problem and so far I have isolated the effective cause down to Permissions or change thereof.

/

 

Hello, I doubt anyone here is going to help you with individual permissions changes in this scenario, but you may be lucky.

For me, my reply stands. Sorry.

 

Needle in a haystack ... without details on what you changed and massive amount of time and dialog, your best bet is to clean install.

If you want to find the holy grail you'll need to be more attentive to troubleshooting.

After a clean install
Make a backup
perform the same things, step-by-step, that you did to create the issue.
When the issue returns, you know what step caused it.
Good luck, I don't have anything else to offer.

 

If you want to find the holy grail you'll need to be more attentive to troubleshooting.

After a clean installMake a backup
perform the same things, step-by-step, that you did to create the issue.
When the issue returns, you know what step caused it.
Good luck, I don't have anything else to offer.[/QUOTE]

Well I know you dont like too many words - so here comes facts without BS. The only log I didn't read was logs from CBS.

Looks like this :

2016-05-11 17:12:37, Info CSI 00000ee3 [DIRSD OWNER WARNING] Directory [l:31 ml:32]"\??\C:\Windows\System32\com\dmp" is not owned but specifies SDDL in component Microsoft-Windows-COM-ComPlus-Runtime, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

AND

2016-05-11 17:14:26, Info CSI 00001588 Error - Overlap: Duplicate ownership for directory [l:29]"\??\C:\Windows\System32\ja-JP" in component Microsoft-Windows-Font-FMS.Resources, version 10.0.10586.0, arch amd64, culture [l:5]"ja-jp", nonSxS, pkt {l:8 b:31bf3856ad364e35}

In total 55 errors. I cant attach log as it exceeds forum limit.

Not bad for lack of troubleshooting *Smile) I erased my profile with full read-/writeaccess under security and advanced permissions, ran CCleaner as administrator. Rebooted - problem solved.

 

*Wink I don't mind too many words - you should see some of my posts

The CBS log entries you posted are not anything to be concerned about.
[DIRSD OWNER WARNING] basically states that C:\Windows\System32\com\dmp is not owned.
SSDL provides the ACL

The Duplicate ownership entry is for Japanese (ja-JP) fonts
Both are Info type entries and can safely be ignored. The other 53 log entries are most likely font or language related - these are known issues in Win10 and will eventually go away.

see: SFC /SCANNOW Command - System File Checker
<<OPTION THREE >>
How to See and Read Only the "SFC" Scan Results from the CBS.LOG

That shows you how to pull the [SR] records out of the log - those records tell you what could not be repaired.
If there are any [SR] records - please post the sfcdetails.txt

Yes, not bad at all - you solved the issue.
*Cool

 

Slartybart : That was an AWESOME response - let me show you the results :

CSI 00005621 [SR] Cannot repair member file [l:24]"System Configuration.lnk" of Microsoft-Windows-MsConfig-Exe, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
CSI 00005624 [SR] Cannot repair member file [l:24]"System Configuration.lnk" of Microsoft-Windows-MsConfig-Exe, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
CSI 00005625 [SR] This component was referenced by [l:163]"Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd64~~10.0.10586.0.Microsoft-Windows-Client-Features-Package-AutoMerged-base-Deployment"
CSI 00005628 [SR] Could not reproject corrupted file [l:77 ml:78]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools"\[l:24]"System Configuration.lnk"; source file in store is also corrupted
CSI 0000562a [SR] Repair complete
CSI 0000562b [SR] Committing transaction
CSI 00005630 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

So - alas the problems are not yet resolved - BUT the post also mentions to extract files from the Windows 10 Image - so I'm jumping on that one. I've included the entire sfcdetails.txt.

Tried repeated sfc /scannow (5X) and the DISM /Cleanup-Image (+restorehealth) - no results.
sfcdetails.txt

 

Pulling replacement files from the source is a bit tricky it can be done, but the component store is not corrected. The file is replaced, but the store still has mismatches - too detailed to cover that in a few posts on a forum.

Try this method and post the results (success or failure)

DISM - Repair Windows 10 Image - Windows 10 Forums
(either Command Prompt or PowerShell method)
6. To Use DISM /RestoreHealth /Source:wim Command
(depending out how your Win10 install was created, the source might be an ESD file - the tutorial covers that in the blue notes.

Then run SFC Command - Run in Windows 10 - Windows 10 Forums

If the resulting screen indicates corruption, post the sfcdetails.txt
SFC Command - Run in Windows 10 - Windows 10 Forums
there is a notation regarding opencl.dll - it is a known issue with SFC reporting only - MS is working on fixing it.

 

On second look .. the sfcdetails.txt file in post# 8 only shows a store hash mismatch for a Start menu shortcut (System Configuration.lnk) in the Administrative Tools category.

This is not a critical file, just a shortcut. The DISM command I gave you in my previous post should fix that, but ... if it doesn't it is not critical - the entries are all Info type.

Info [SR] Cannot repair member file [l:24]"System Configuration.lnk" of Microsoft-Windows-MsConfig-Exe, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
Info [SR] Cannot repair member file [l:24]"System Configuration.lnk" of Microsoft-Windows-MsConfig-Exe, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
Info [SR] This component was referenced by [l:163]"Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd64~~10.0.10586.0.Microsoft-Windows-Client-Features-Package-AutoMerged-base-Deployment"
Info [SR] Could not reproject corrupted file [l:77 ml:78]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools"\[l:24]"System Configuration.lnk"; source file in store is also corrupted
Info [SR] Verifying 8 components
Info [SR] Repairing 1 components
Info [SR] Cannot repair member file [l:24]"System Configuration.lnk" of Microsoft-Windows-MsConfig-Exe, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
Info [SR] Cannot repair member file [l:24]"System Configuration.lnk" of Microsoft-Windows-MsConfig-Exe, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
Info [SR] This component was referenced by [l:163]"Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd64~~10.0.10586.0.Microsoft-Windows-Client-Features-Package-AutoMerged-base-Deployment"
Info [SR] Could not reproject corrupted file [l:77 ml:78]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools"\[l:24]"System Configuration.lnk"; source file in store is also corrupted
Info [SR] Repair complete
Info [SR] Committing transaction
Info [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

 

Slartybart : You're brilliant.. though the problems persist - I'm getting so much closer. Following your advice via Forum posts, I opted to do the :

Dism /Online /Cleanup-Image /RestoreHealth /Source:esd.\sources\Install.esd:1 /limitaccess

(My image is a ESD-USB) Result = "Image could not be located"

I've included logs and a screenshot - the previous results you clarified made sense (fonts and neglible directories) but what frag do you make of the results in the dism log ?CBS.logdism.log

 

Ok, a couple of things that I see

1) Dism /Online /Cleanup-Image /RestoreHealth /Source:esd.\sources\Install.esd:1 /limitaccess
In you explanatory text, there's a period (.) instead of a colon ) after the drive (D) parameter

2) The screen shot shows that you only entered
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:

3) The Checkhealth command says it is repairable.

Try this

Launch Command Prompt (Admin)
enter the following command (assuming the ESD is drive letter D)

Dism /Online /Cleanup-Image /RestoreHealth /Limitaccess /Source:esd:\sources\Install.esd:1
To avoid typos (everybody makes 'em), you can copy the line above and paste it into the Command Prompt window.

 

Slartybart : When I posted - it was with the intent of "I'll show him/her it's not that simple and I have done everything right!!" - well I have done everything from the last post you wrote about - and now - it works. So I officially apologize - and thank you for every ounce of patience trying to direct an stubborn ego from a far.

PROBLEM SOLVED!