From 4874d7581665938289d81d31af05a42c231070f2 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Mon, 8 May 2017 12:18:54 -0700 Subject: [PATCH 1/3] updated upgrade error doc per Kaushik --- .../resolve-windows-10-upgrade-errors.md | 35 +++++++++++++++++++ windows/security/TOC.md | 26 ++++++++++++++ 2 files changed, 61 insertions(+) create mode 100644 windows/security/TOC.md diff --git a/windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md b/windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md index 2ec92b3418..6182c5a89f 100644 --- a/windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md +++ b/windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md @@ -825,6 +825,41 @@ Download and run the media creation tool. See [Download windows 10](https://www. + +0x80240FFF +Occurs when update synchronization fails. It can occur when you are using Windows Server Update Services on its own or when it is integrated with System Center Configuration Manager. If you enable update synchronization before you install hotfix 3095113, WSUS doesn't recognize the Upgrades classification and instead treats the upgrade like a regular update. + You can prevent this by installing hotfix 3095113 before you enable update synchronization. However, if you have already run into this problem, do the following: + +
    +
  1. Disable the Upgrades classification.
    2. +
  2. Install hotfix 3095113.
    3. +
  3. Delete previously synched updates.
    4. +
  4. Enable the Upgrades classification.
    5. +
  5. Perform a full synch.
    6. +
+

For detailed information on how to run these steps check out How to delete upgrades in WSUS.

+ + + + +0x8007007E +Occurs when update synchronization fails because you do not have hotfix 3095113 installed before you enable update synchronization. Specifically, the CopyToCache operation fails on clients that have already downlaoded the upgrade because Windows Server Update Services has bad metadata related to the upgrade. It can occur when you are using standalone Windows Server Update Services or when WSUS is integrated with System Center Configuration Manager. + Use the following steps to repair Windows Server Update Services. You must run these steps on each WSUS server that synched metadate before you installed the hotfix. + +
    +
  1. Stop the Windows Update service. Sign in as a user with administrative privileges, and then do the following: +
      +
    1. Open Administrative Tools from the Control Panel.
      2. +
    2. Double-click Services.
      3. +
    3. Find the Windows Update service, right-click it, and then click Stop.
      4. +
    +
    2. +
  2. Delete all files and folders under c:\Windows\SoftwareDistribution\DataStore.
    3. +
  3. Restart the Windows Update service.
    4. +
+ + + ### Other error codes diff --git a/windows/security/TOC.md b/windows/security/TOC.md new file mode 100644 index 0000000000..8bca881506 --- /dev/null +++ b/windows/security/TOC.md @@ -0,0 +1,26 @@ +# [Windows 10 security on modern devices](index.md) +## [Device protection](/windows/device-security/index) +### VIrtualization-based security +### UEFI Secure Boot +### Windows Trusted Boot +### Windows Update +### Trusted Platform Module +## [Threat resistance](/windows/threat-protection) +### Device Guard +### Windows Defender Antivirus +### Windows Firewall +### Windows Defender Smartscreen +## Identity protection +### Credential Guard +### Windows Hello companion devices +### Windows Hello +## Information protection +### Device encryption +### Windows Information Protection +### Bitlocker administration and monitoring +### Bitlocker +### Bitlocker to Go +## Breach detection, investigation, & response +### Security management +### Conditional access +### Windows De From 87a6904f4285e7333a978805cfea19c4072fc21d Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Mon, 8 May 2017 12:19:53 -0700 Subject: [PATCH 2/3] removed erroneous folder --- windows/security/TOC.md | 26 -------------------------- 1 file changed, 26 deletions(-) delete mode 100644 windows/security/TOC.md diff --git a/windows/security/TOC.md b/windows/security/TOC.md deleted file mode 100644 index 8bca881506..0000000000 --- a/windows/security/TOC.md +++ /dev/null @@ -1,26 +0,0 @@ -# [Windows 10 security on modern devices](index.md) -## [Device protection](/windows/device-security/index) -### VIrtualization-based security -### UEFI Secure Boot -### Windows Trusted Boot -### Windows Update -### Trusted Platform Module -## [Threat resistance](/windows/threat-protection) -### Device Guard -### Windows Defender Antivirus -### Windows Firewall -### Windows Defender Smartscreen -## Identity protection -### Credential Guard -### Windows Hello companion devices -### Windows Hello -## Information protection -### Device encryption -### Windows Information Protection -### Bitlocker administration and monitoring -### Bitlocker -### Bitlocker to Go -## Breach detection, investigation, & response -### Security management -### Conditional access -### Windows De From 093e3bc55a37fe4ec1b45ae2e0850248fa36b809 Mon Sep 17 00:00:00 2001 From: Liza Poggemeyer Date: Mon, 8 May 2017 12:55:23 -0700 Subject: [PATCH 3/3] Revert "Update to upgrade errors/events article" --- .../resolve-windows-10-upgrade-errors.md | 35 ------------------- 1 file changed, 35 deletions(-) diff --git a/windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md b/windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md index 6182c5a89f..2ec92b3418 100644 --- a/windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md +++ b/windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md @@ -825,41 +825,6 @@ Download and run the media creation tool. See [Download windows 10](https://www. - -0x80240FFF -Occurs when update synchronization fails. It can occur when you are using Windows Server Update Services on its own or when it is integrated with System Center Configuration Manager. If you enable update synchronization before you install hotfix 3095113, WSUS doesn't recognize the Upgrades classification and instead treats the upgrade like a regular update. - You can prevent this by installing hotfix 3095113 before you enable update synchronization. However, if you have already run into this problem, do the following: - -
    -
  1. Disable the Upgrades classification.
    2. -
  2. Install hotfix 3095113.
    3. -
  3. Delete previously synched updates.
    4. -
  4. Enable the Upgrades classification.
    5. -
  5. Perform a full synch.
    6. -
-

For detailed information on how to run these steps check out How to delete upgrades in WSUS.

- - - - -0x8007007E -Occurs when update synchronization fails because you do not have hotfix 3095113 installed before you enable update synchronization. Specifically, the CopyToCache operation fails on clients that have already downlaoded the upgrade because Windows Server Update Services has bad metadata related to the upgrade. It can occur when you are using standalone Windows Server Update Services or when WSUS is integrated with System Center Configuration Manager. - Use the following steps to repair Windows Server Update Services. You must run these steps on each WSUS server that synched metadate before you installed the hotfix. - -
    -
  1. Stop the Windows Update service. Sign in as a user with administrative privileges, and then do the following: -
      -
    1. Open Administrative Tools from the Control Panel.
      2. -
    2. Double-click Services.
      3. -
    3. Find the Windows Update service, right-click it, and then click Stop.
      4. -
    -
    2. -
  2. Delete all files and folders under c:\Windows\SoftwareDistribution\DataStore.
    3. -
  3. Restart the Windows Update service.
    4. -
- - - ### Other error codes