mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 02:43:43 +00:00
Merge pull request #4180 from nschonni/fix--MD033/no-inline-html
fix: MD033/no-inline-html
This commit is contained in:
Daniel Simpson
GitHub
@ -58,7 +58,7 @@ On a test machine:
|
||||
1. **Install the Microsoft Store for Business application you previously added** to your image.
|
||||
2. **Pin these apps to the Start screen**, by typing the name of the app, right-clicking and selecting **Pin to Start**.
|
||||
3. Open Windows PowerShell with administrator privileges.
|
||||
4. Use `Export-StartLayout -path <path><file name>.xml` where *<path><file name>* is the path and name of the xml file your will later import into your Windows Image.
|
||||
4. Use `Export-StartLayout -path <path><file name>.xml` where *\<path>\<file name>* is the path and name of the xml file your will later import into your Windows Image.
|
||||
5. Copy the XML file you created to a location accessible by the machine you previously used to add Store applications to your image.
|
||||
|
||||
Now, on the machine where your image file is accessible:
|
||||
|
||||
@ -188,7 +188,7 @@ To work around this, click the **App Reliability** tab above the results to see
|
||||
#### Clicking "See all…" from the App Reliability Events blade followed by clicking an app from the expanded list results in raw records instead of the App Reliability view
|
||||
To work around this, replace all of the text in the Log Search query box with the following:
|
||||
|
||||
*DHAppReliability | where AppFileDisplayName == "<Name of app as it appeared in the list>"*
|
||||
*DHAppReliability | where AppFileDisplayName == "\<Name of app as it appeared in the list>"*
|
||||
|
||||
For example:
|
||||
|
||||
|
||||
@ -27,8 +27,8 @@ Use the following information to deploy feature updates during a maintenance win
|
||||
1. In the Configuration Manager console, choose **Assets and Compliance> Device Collections**.
|
||||
2. In the **Device Collections** list, select the collection for which you intended to deploy the feature update(s).
|
||||
3. On the **Home** tab, in the **Properties** group, choose **Properties**.
|
||||
4. In the **Maintenance Windows** tab of the <collection name> Properties dialog box, choose the New icon.
|
||||
5. Complete the <new> Schedule dialog.
|
||||
4. In the **Maintenance Windows** tab of the `<collection name>` Properties dialog box, choose the New icon.
|
||||
5. Complete the `<new>` Schedule dialog.
|
||||
6. Select from the Apply this schedule to drop-down list.
|
||||
7. Choose **OK** and then close the **\<collection name\> Properties** dialog box.
|
||||
|
||||
|
||||
@ -26,8 +26,8 @@ The following table provides information about common errors you might run into
|
||||
| 0x80242006 | WU_E_UH_INVALIDMETADATA | A handler operation could not be completed because the update contains invalid metadata. | Rename Software Redistribution Folder and attempt to download the updates again: <br>Rename the following folders to \*.BAK: <br>- %systemroot%\system32\catroot2 <br><br>To do this, type the following commands at a command prompt. Press ENTER after you type each command.<br>- Ren %systemroot%\SoftwareDistribution\DataStore \*.bak<br>- Ren %systemroot%\SoftwareDistribution\Download \*.bak<br>Ren %systemroot%\system32\catroot2 \*.bak |
|
||||
| 0x80070BC9 | ERROR_FAIL_REBOOT_REQUIRED | The requested operation failed. A system reboot is required to roll back changes made. | Ensure that we do not have any policies that control the start behavior for the Windows Module Installer. This service should not be hardened to any start value and should be managed by the OS. |
|
||||
| 0x80200053 | BG_E_VALIDATION_FAILED | NA | Ensure that there is no Firewalls that filter downloads. The Firewall filtering may lead to invalid responses being received by the Windows Update Client.<br><br>If the issue still persists, run the [WU reset script](https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc). |
|
||||
| 0x80072EE2 | WININET_E_TIMEOUT | The operation timed out | This error message can be caused if the computer isn't connected to Internet. To fix this issue, following these steps: make sure these URLs are not blocked: <br> http://<em>.update.microsoft.com<br>https://</em>.update.microsoft.com <br><http://download.windowsupdate.com> <br><br>Additionally , you can take a network trace and see what is timing out. <Refer to Firewall Troubleshooting scenario> |
|
||||
| 0x80072EFD <br>0x80072EFE <br>0x80D02002 | TIME OUT ERRORS | The operation timed out | Make sure there are no firewall rules or proxy to block Microsoft download URLs. <br>Take a network monitor trace to understand better. <Refer to Firewall Troubleshooting scenario> |
|
||||
| 0x80072EE2 | WININET_E_TIMEOUT | The operation timed out | This error message can be caused if the computer isn't connected to Internet. To fix this issue, following these steps: make sure these URLs are not blocked: <br> http://<em>.update.microsoft.com<br>https://</em>.update.microsoft.com <br><http://download.windowsupdate.com> <br><br>Additionally , you can take a network trace and see what is timing out. \<Refer to Firewall Troubleshooting scenario> |
|
||||
| 0x80072EFD <br>0x80072EFE <br>0x80D02002 | TIME OUT ERRORS | The operation timed out | Make sure there are no firewall rules or proxy to block Microsoft download URLs. <br>Take a network monitor trace to understand better. \<Refer to Firewall Troubleshooting scenario> |
|
||||
| 0X8007000D | ERROR_INVALID_DATA | Indicates invalid data downloaded or corruption occurred. | Attempt to re-download the update and initiate installation. |
|
||||
| 0x8024A10A | USO_E_SERVICE_SHUTTING_DOWN | Indicates that the WU Service is shutting down. | This may happen due to a very long period of time of inactivity, a system hang leading to the service being idle and leading to the shutdown of the service. Ensure that the system remains active and the connections remain established to complete the upgrade. |
|
||||
| 0x80240020 | WU_E_NO_INTERACTIVE_USER | Operation did not complete because there is no logged-on interactive user. | Please login to the system to initiate the installation and allow the system to be rebooted. |
|
||||
|
||||
@ -142,7 +142,7 @@ Therefore, Windows Setup failed because it was not able to migrate the corrupt f
|
||||
27:00, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped
|
||||
27:00, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped
|
||||
27:00, Info SP ExecuteProgress: Elapsed events:1 of 4, Percent: 12
|
||||
27:00, Info [0x0802c6] MIG Processing GATHER for migration unit: <System>\UpgradeFramework (CMXEAgent)
|
||||
27:00, Info [0x0802c6] MIG Processing GATHER for migration unit: <System>\UpgradeFramework (CMXEAgent)
|
||||
27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570]
|
||||
27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570]
|
||||
27:08, Info SP ExecuteProgress: Elapsed events:2 of 4, Percent: 25
|
||||
|
||||
@ -179,5 +179,5 @@ Error creating or updating registry key: **CommercialId** at **HKLM:\SOFTWARE\Mi
|
||||
>
|
||||
> Then run the Enterprise Config script (RunConfig.bat) again.
|
||||
>
|
||||
> If the script still fails, then send mail to <strong>uasupport@microsoft.com</strong> including log files from the RunConfig.bat script. These log files are stored on the drive that is specified in the RunConfig.bat file. By default this is set to **%SystemDrive%\UADiagnostics**. The log file is named with the format **UA_yyyy_mm_dd_hh_mm_ss_machineID.txt**. There will be some additional logs generated under your **<system drive>\Windows\Temp** directory with the names similar to **AslLog_....txt**. You should send those logs as well.
|
||||
> If the script still fails, then send mail to <strong>uasupport@microsoft.com</strong> including log files from the RunConfig.bat script. These log files are stored on the drive that is specified in the RunConfig.bat file. By default this is set to **%SystemDrive%\UADiagnostics**. The log file is named with the format **UA_yyyy_mm_dd_hh_mm_ss_machineID.txt**. There will be some additional logs generated under your **\<system drive>\Windows\Temp** directory with the names similar to **AslLog_....txt**. You should send those logs as well.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user