The results are often problematic and unreliable. No method is supported to install Start Appx files. This can be rolling back the update, resetting the PC to defaults (where there is a choice to save to delete user data), or restoring from backup. If Start is not installed, then the fastest resolution is to revert to a known good configuration. Get-AppXPackage -Name įailure messages will appear if they aren't installed The way to check for this problem is to look for output from these two PS commands: If Start was working and just fails intermittently, it's likely that Start is installed correctly, but the issue occurs downstream. If Start fails immediately after a feature update, on thing to check is if the App package failed to install successfully.
Did the issue start immediately after an update? Ways to check:. Is the system running the latest Feature and Cumulative Monthly update?. For issues where the Start menu or subcomponent isn't working, you can do some quick tests to narrow down where the issue may reside. When troubleshooting basic Start issues (and for the most part, all other Windows apps), there are a few things to check if they are not working as expected. Other issues - Customization, domain policies, deployment issues. Clean boot may help identify if the issue is related to additional software. If a background application or service hangs, Start will not have resources to respond in time. These are the hardest issues to identify as there are few events logged, but behavior is typically intermittent or recovers with a reboot. Hangs - in Shell Experience host or related. The other option is to get a dump of the process when it crashes and depending on comfort level, review the dump in the debugger, or have support review the data. Determining permissions issues can be time consuming but a SysInternals tool called Procmon will show Access Denied. This can be a code defect or related to missing or altered permissions to files or registry keys by a program or incorrect security tightening configurations. Crashes in Shell Experience Host or related can be found in System or Application event logs. Behavior is intermittent depending on available resources. Symptoms include: High CPU utilization, disk contention, memory resources. Performance issues - More common with older hardware, low-powered machines. Reset, restore from backup, or rollback to recover. This failure is consistent and usually permanent. Deployment/Install issues - Easiest to identify but difficult to recover. Start failures can be organized into these categories:
0 kommentar(er)
