mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
acrolinx fixes
This commit is contained in:
@ -20,7 +20,7 @@ manager: dansimp
|
|||||||
|
|
||||||
Cortana will respond with the information from Bing.
|
Cortana will respond with the information from Bing.
|
||||||
|
|
||||||
:::image type="content" source="../screenshot5.png" alt-text="Screenshot: Cortana showing current time in Hyderbad":::
|
:::image type="content" source="../screenshot5.png" alt-text="Screenshot: Cortana showing current time in Hyderabad":::
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>This scenario requires Bing Answers to be enabled. To learn more, see [Set up and configure the Bing Answers feature](https://docs.microsoft.com/windows/configuration/cortana-at-work/set-up-and-test-cortana-in-windows-10#set-up-and-configure-the-bing-answers-feature).
|
>This scenario requires Bing Answers to be enabled. To learn more, see [Set up and configure the Bing Answers feature](https://docs.microsoft.com/windows/configuration/cortana-at-work/set-up-and-test-cortana-in-windows-10#set-up-and-configure-the-bing-answers-feature).
|
@ -1,6 +1,6 @@
|
|||||||
---
|
---
|
||||||
title: Use MDM Bridge WMI Provider to create a Windows 10 kiosk (Windows 10)
|
title: Use MDM Bridge WMI Provider to create a Windows 10 kiosk (Windows 10)
|
||||||
description: Environments that use Windows Management Instrumentation (WMI)can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
|
description: Environments that use Windows Management Instrumentation (WMI) can use the MDM Bridge WMI Provider to configure the MDM_AssignedAccess class.
|
||||||
ms.assetid: 428680AE-A05F-43ED-BD59-088024D1BFCC
|
ms.assetid: 428680AE-A05F-43ED-BD59-088024D1BFCC
|
||||||
ms.reviewer:
|
ms.reviewer:
|
||||||
manager: dansimp
|
manager: dansimp
|
||||||
@ -22,9 +22,9 @@ ms.topic: article
|
|||||||
|
|
||||||
- Windows 10 Pro, Enterprise, and Education
|
- Windows 10 Pro, Enterprise, and Education
|
||||||
|
|
||||||
Environments that use [Windows Management Instrumentation (WMI)](https://msdn.microsoft.com/library/aa394582.aspx) can use the [MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/desktop/dn905224.aspx) to configure the MDM_AssignedAccess class. See [PowerShell Scripting with WMI Bridge Provider](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/using-powershell-scripting-with-the-wmi-bridge-provider) for more details about using a PowerShell script to configure AssignedAccess.
|
Environments that use [Windows Management Instrumentation (WMI)](https://msdn.microsoft.com/library/aa394582.aspx) can use the [MDM Bridge WMI Provider](https://msdn.microsoft.com/library/windows/desktop/dn905224.aspx) to configure the MDM_AssignedAccess class. For more information about using a PowerShell script to configure AssignedAccess, see [PowerShell Scripting with WMI Bridge Provider](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/using-powershell-scripting-with-the-wmi-bridge-provider).
|
||||||
|
|
||||||
Here’s an example to set AssignedAccess configuration:
|
Here's an example to set AssignedAccess configuration:
|
||||||
|
|
||||||
1. Download the [psexec tool](https://technet.microsoft.com/sysinternals/bb897553.aspx).
|
1. Download the [psexec tool](https://technet.microsoft.com/sysinternals/bb897553.aspx).
|
||||||
2. Run `psexec.exe -i -s cmd.exe`.
|
2. Run `psexec.exe -i -s cmd.exe`.
|
||||||
|
@ -255,7 +255,7 @@ This sample demonstrates that both UWP and Win32 apps can be configured to autom
|
|||||||
```
|
```
|
||||||
|
|
||||||
## [Preview] Global Profile Sample XML
|
## [Preview] Global Profile Sample XML
|
||||||
Global Profile is currently supported in Windows 10 Insider Preview (20H1 builds). Global Profile is designed for scenarios where a user does not have a designated profile, yet IT Admin still wants the user to run in lock down mode, or used as mitigation when a profile cannot be determined for an user.
|
Global Profile is currently supported in Windows 10 Insider Preview (20H1 builds). Global Profile is designed for scenarios where a user does not have a designated profile, yet IT Admin still wants the user to run in lockdown mode, or used as mitigation when a profile cannot be determined for a user.
|
||||||
|
|
||||||
This sample demonstrates that only a global profile is used, no active user configured. Global profile will be applied when every non-admin account logs in
|
This sample demonstrates that only a global profile is used, no active user configured. Global profile will be applied when every non-admin account logs in
|
||||||
```xml
|
```xml
|
||||||
@ -309,7 +309,7 @@ This sample demonstrates that only a global profile is used, no active user conf
|
|||||||
</AssignedAccessConfiguration>
|
</AssignedAccessConfiguration>
|
||||||
```
|
```
|
||||||
|
|
||||||
Below sample shows dedicated profile and global profile mixed usage, aauser would use one profile, everyone else that's non-admin will use another profile.
|
Below sample shows dedicated profile and global profile mixed usage, a user would use one profile, everyone else that's non-admin will use another profile.
|
||||||
```xml
|
```xml
|
||||||
<?xml version="1.0" encoding="utf-8" ?>
|
<?xml version="1.0" encoding="utf-8" ?>
|
||||||
<AssignedAccessConfiguration
|
<AssignedAccessConfiguration
|
||||||
@ -396,7 +396,7 @@ Below sample shows dedicated profile and global profile mixed usage, aauser woul
|
|||||||
## [Preview] Folder Access sample xml
|
## [Preview] Folder Access sample xml
|
||||||
In Windows 10, version 1809, folder access is locked down so that when common file dialog is opened, IT Admin can specify if the user has access to the Downloads folder, or no access to any folder at all. This restriction has been redesigned for finer granulatity and easier use, and is available in Windows 10 Insider Preview (19H2, 20H1 builds).
|
In Windows 10, version 1809, folder access is locked down so that when common file dialog is opened, IT Admin can specify if the user has access to the Downloads folder, or no access to any folder at all. This restriction has been redesigned for finer granulatity and easier use, and is available in Windows 10 Insider Preview (19H2, 20H1 builds).
|
||||||
|
|
||||||
IT Admin now can specify user access to Downloads folder, Removable drives, or no restrictions at all. Note that Downloads and Removable Drives can be allowed at the same time.
|
IT Admin now can specify user access to Downloads folder, Removable drives, or no restrictions at all. Downloads and Removable Drives can be allowed at the same time.
|
||||||
|
|
||||||
```xml
|
```xml
|
||||||
<?xml version="1.0" encoding="utf-8" ?>
|
<?xml version="1.0" encoding="utf-8" ?>
|
||||||
@ -889,7 +889,7 @@ Schema for Windows 10 Insider Preview (19H2, 20H1 builds)
|
|||||||
</xs:schema>
|
</xs:schema>
|
||||||
```
|
```
|
||||||
|
|
||||||
To authorize a compatible configuration XML that includes elements and attributes from Windows 10, version 1809 or newer, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the auto-launch feature which is added in Windows 10, version 1809, use the following sample. Notice an alias r1809 is given to the 201810 namespace for Windows 10, version 1809, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
|
To authorize a compatible configuration XML that includes elements and attributes from Windows 10, version 1809 or newer, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the autolaunch feature that was added in Windows 10, version 1809, use the following sample. Notice an alias r1809 is given to the 201810 namespace for Windows 10, version 1809, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
|
||||||
```xml
|
```xml
|
||||||
<AssignedAccessConfiguration
|
<AssignedAccessConfiguration
|
||||||
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
|
||||||
|
@ -12,7 +12,7 @@ manager: dansimp
|
|||||||
ms.topic: troubleshooting
|
ms.topic: troubleshooting
|
||||||
---
|
---
|
||||||
|
|
||||||
# Troubleshoot Start Menu errors
|
# Troubleshoot Start menu errors
|
||||||
|
|
||||||
Start failures can be organized into these categories:
|
Start failures can be organized into these categories:
|
||||||
|
|
||||||
@ -24,29 +24,29 @@ Start failures can be organized into these categories:
|
|||||||
|
|
||||||
## Basic troubleshooting
|
## Basic troubleshooting
|
||||||
|
|
||||||
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. When experiencing issues where the Start Menu or sub-component are not working, there are 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. 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.
|
||||||
|
|
||||||
### Check the OS and update version
|
### Check the OS and update version
|
||||||
|
|
||||||
- Is the system running the latest Feature and Cumulative Monthly update?
|
- Is the system running the latest Feature and Cumulative Monthly update?
|
||||||
- Did the issue start immediately after an update? Ways to check:
|
- Did the issue start immediately after an update? Ways to check:
|
||||||
- Powershell:[System.Environment]::OSVersion.Version
|
- PowerShell:[System.Environment]::OSVersion.Version
|
||||||
- WinVer from CMD.exe
|
- WinVer from CMD.exe
|
||||||
|
|
||||||
### Check if Start is installed
|
### Check if Start is installed
|
||||||
|
|
||||||
- If Start fails immediately after a feature update, on thing to check is if the App package failed to install successfully.
|
- If Start fails immediately after a feature update, on thing to check is if the App package failed to install successfully.
|
||||||
|
|
||||||
- If Start was working and just fails intermittently, it's likely that Start is installed correctly, but the issue occurs downstream. The way to check for this 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. The way to check for this problem is to look for output from these two PS commands:
|
||||||
|
|
||||||
- `get-AppXPackage -Name Microsoft.Windows.ShellExperienceHost`
|
- `get-AppXPackage -Name Microsoft.Windows.ShellExperienceHost`
|
||||||
- `get-AppXPackage -Name Microsoft.Windows.Cortana`
|
- `get-AppXPackage -Name Microsoft.Windows.Cortana`
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Failure messages will appear if they are not installed
|
Failure messages will appear if they aren't installed
|
||||||
|
|
||||||
- If Start is not installed the fastest resolution is to revert to a known good configuration. 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. There is no supported method to install Start Appx files. The results are often problematic and unreliable.
|
- If Start is not installed, then the fastest resolution is to revert to a known good configuration. 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. There is no supported method to install Start Appx files. The results are often problematic and unreliable.
|
||||||
|
|
||||||
### Check if Start is running
|
### Check if Start is running
|
||||||
|
|
||||||
@ -54,7 +54,7 @@ If either component is failing to start on boot, reviewing the event logs for er
|
|||||||
- `get-process -name shellexperiencehost`
|
- `get-process -name shellexperiencehost`
|
||||||
- `get-process -name searchui`
|
- `get-process -name searchui`
|
||||||
|
|
||||||
If it is installed but not running, test booting into safe mode or use MSCONFIG to eliminate 3rd party or additional drivers and applications.
|
If it is installed but not running, test booting into safe mode or use MSCONFIG to eliminate third-party or additional drivers and applications.
|
||||||
|
|
||||||
### Check whether the system a clean install or upgrade
|
### Check whether the system a clean install or upgrade
|
||||||
|
|
||||||
@ -76,9 +76,9 @@ If these events are found, Start is not activated correctly. Each event will hav
|
|||||||
|
|
||||||
### Other things to consider
|
### Other things to consider
|
||||||
|
|
||||||
When did this start?
|
When did the problem start?
|
||||||
|
|
||||||
- Top issues for Start Menu failure are triggered
|
- Top issues for Start menu failure are triggered
|
||||||
- After an update
|
- After an update
|
||||||
- After installation of an application
|
- After installation of an application
|
||||||
- After joining a domain or applying a domain policy
|
- After joining a domain or applying a domain policy
|
||||||
@ -87,7 +87,7 @@ When did this start?
|
|||||||
- Start or related component crashes or hangs
|
- Start or related component crashes or hangs
|
||||||
- Customization failure
|
- Customization failure
|
||||||
|
|
||||||
To narrow this down further, it's good to note:
|
To narrow down the problem further, it's good to note:
|
||||||
|
|
||||||
- What is the install background?
|
- What is the install background?
|
||||||
- Was this a deployment, install from media, other
|
- Was this a deployment, install from media, other
|
||||||
@ -103,7 +103,7 @@ To narrow this down further, it's good to note:
|
|||||||
- Some Group Policies intended for Windows 7 or older have been known to cause issues with Start
|
- Some Group Policies intended for Windows 7 or older have been known to cause issues with Start
|
||||||
- Untested Start Menu customizations can cause unexpected behavior by typically not complete Start failures.
|
- Untested Start Menu customizations can cause unexpected behavior by typically not complete Start failures.
|
||||||
|
|
||||||
- Is this a virtualized environment?
|
- Is the environment virtualized?
|
||||||
- VMware
|
- VMware
|
||||||
- Citrix
|
- Citrix
|
||||||
- Other
|
- Other
|
||||||
@ -123,13 +123,13 @@ To narrow this down further, it's good to note:
|
|||||||
- Microsoft-Windows-CloudStore*
|
- Microsoft-Windows-CloudStore*
|
||||||
|
|
||||||
|
|
||||||
- Check for crashes that may be related to Start (explorer.exe, taskbar, etc)
|
- Check for crashes that may be related to Start (explorer.exe, taskbar, and so on)
|
||||||
- Application log event 1000, 1001
|
- Application log event 1000, 1001
|
||||||
- Check WER reports
|
- Check WER reports
|
||||||
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
|
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
|
||||||
- C:\ProgramData\Micrt\Windowsosof\WER\ReportQueue\
|
- C:\ProgramData\Micrt\Windowsosof\WER\ReportQueue\
|
||||||
|
|
||||||
If there is a component of Start that is consistently crashing, capture a dump which can be reviewed by Microsoft Support.
|
If there is a component of Start that is consistently crashing, capture a dump that can be reviewed by Microsoft Support.
|
||||||
|
|
||||||
## Common errors and mitigation
|
## Common errors and mitigation
|
||||||
|
|
||||||
@ -169,7 +169,8 @@ The PDC registry key is:
|
|||||||
**Type**=dword:00000001
|
**Type**=dword:00000001
|
||||||
|
|
||||||
In addition to the listed dependencies for the service, Background Tasks Infrastructure Service requires the Power Dependency Coordinator Driver to be loaded. If the PDC does not load at boot, Background Tasks Infrastructure Service will fail and affect Start Menu.
|
In addition to the listed dependencies for the service, Background Tasks Infrastructure Service requires the Power Dependency Coordinator Driver to be loaded. If the PDC does not load at boot, Background Tasks Infrastructure Service will fail and affect Start Menu.
|
||||||
Events for both PDC and Background Tasks Infrastructure Service will be recorded in the event logs. PDC should not be disabled or deleted. BrokerInfrastructure is an automatic service. This Service is required for all these operating Systems as running to have a stable Start Menu.
|
|
||||||
|
Events for both PDC and Background Tasks Infrastructure Service will be recorded in the event logs. PDC shouldn't be disabled or deleted. BrokerInfrastructure is an automatic service. This Service is required for all these operating Systems as running to have a stable Start Menu.
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>You cannot stop this automatic service when machine is running (C:\windows\system32\svchost.exe -k DcomLaunch -p).
|
>You cannot stop this automatic service when machine is running (C:\windows\system32\svchost.exe -k DcomLaunch -p).
|
||||||
@ -179,17 +180,17 @@ Events for both PDC and Background Tasks Infrastructure Service will be recorded
|
|||||||
|
|
||||||
**Cause**: There was a change in the All Apps list between Windows 10, versions 1511 and 1607. These changes mean the original Group Policy and corresponding registry key no longer apply.
|
**Cause**: There was a change in the All Apps list between Windows 10, versions 1511 and 1607. These changes mean the original Group Policy and corresponding registry key no longer apply.
|
||||||
|
|
||||||
**Resolution**: This issue was resolved in the June 2017 updates. Please update Windows 10, version 1607 to the latest cumulative or feature updates.
|
**Resolution**: This issue was resolved in the June 2017 updates. Update Windows 10, version 1607, to the latest cumulative or feature updates.
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
>When the Group Policy is enabled, the desired behavior also needs to be selected. By default, it is set to **None**.
|
>When the Group Policy is enabled, the desired behavior also needs to be selected. By default, it is set to **None**.
|
||||||
|
|
||||||
|
|
||||||
### Symptom: Application tiles like Alarm, Calculator, and Edge are missing from Start Menu and the Settings app fails to open on Windows 10, version 1709 when a local user profile is deleted
|
### Symptom: Application tiles like Alarm, Calculator, and Edge are missing from Start menu and the Settings app fails to open on Windows 10, version 1709 when a local user profile is deleted
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
**Cause**: This is a known issue where the first-time logon experience is not detected and does not trigger the install of some Apps.
|
**Cause**: This issue is known. The first-time sign-in experience is not detected and does not trigger the install of some apps.
|
||||||
|
|
||||||
**Resolution**: This issue has been fixed for Windows 10, version 1709 in [KB 4089848](https://support.microsoft.com/help/4089848) March 22, 2018—KB4089848 (OS Build 16299.334)
|
**Resolution**: This issue has been fixed for Windows 10, version 1709 in [KB 4089848](https://support.microsoft.com/help/4089848) March 22, 2018—KB4089848 (OS Build 16299.334)
|
||||||
|
|
||||||
@ -202,7 +203,7 @@ Events for both PDC and Background Tasks Infrastructure Service will be recorded
|
|||||||
- Event ID 22 is logged when the xml is malformed, meaning the specified file simply isn’t valid xml.
|
- Event ID 22 is logged when the xml is malformed, meaning the specified file simply isn’t valid xml.
|
||||||
- When editing the xml file, it should be saved in UTF-8 format.
|
- When editing the xml file, it should be saved in UTF-8 format.
|
||||||
|
|
||||||
- Unexpected information: This occurs when possibly trying to add a tile via unexpected or undocumented method.
|
- Unexpected information: This occurs when possibly trying to add a tile via an unexpected or undocumented method.
|
||||||
- **Event ID: 64** is logged when the xml is valid but has unexpected values.
|
- **Event ID: 64** is logged when the xml is valid but has unexpected values.
|
||||||
- For example: The following error occurred while parsing a layout xml file: The attribute 'LayoutCustomizationRestrictiontype' on the element '{http://schemas.microsoft.com/Start/2014/LayoutModification}DefaultLayoutOverride' is not defined in the DTD/Schema.
|
- For example: The following error occurred while parsing a layout xml file: The attribute 'LayoutCustomizationRestrictiontype' on the element '{http://schemas.microsoft.com/Start/2014/LayoutModification}DefaultLayoutOverride' is not defined in the DTD/Schema.
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user