Merge pull request #10480 from MicrosoftDocs/learn-build-service-prodbot/docutune-autopr-20260108-225327-7537884-ignore-build

AB#9112: [BULK] [Bundle-Security] - Scheduled execution to fix known issues (part 8)

Author: v-tappelgate

support/windows-client/group-policy/scenario-guide-gpo-to-map-network-drive-doesn-t-apply-as-expected.md

@@ -132,7 +132,7 @@ In *\<Clientmachinename\>_\<Date_Time\>_GPPREF_User.txt*, we observe that the GP
 
 ```output
 yyyy-mm-dd hh:mm::ss:sss [pid=0x3134,tid=0x4fc] Entering ProcessGroupPolicyExDrives()
-yyyy-mm-dd hh:mm::ss:sss [pid=0x3134,tid=0x4fc] SOFTWARE\Policies\Microsoft\Windows\Group Policy\{5794DAFD-BE60-433f-88A2-1A31939AC01F}
+yyyy-mm-dd hh:mm::ss:sss [pid=0x3134,tid=0x4fc] SOFTWARE\Policies\Microsoft\Windows\Group Policy\{aaaabbbb-0000-cccc-1111-dddd2222eeee}
 ```
 
 The Group Policy Mapped Drives extension identified a GPO that's configured with this extension, and the name is **Mapped-Drive**:

support/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting.md

@@ -74,10 +74,10 @@ Checking the WindowsUpdate.log reveals the following error:
 ```output
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           * START * Finding updates CallerId = Update;taskhostw  Id = 25
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           Online = Yes; Interactive = No; AllowCachedResults = No; Ignore download priority = No
-YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           ServiceID = {855E8A7C-ECB4-4CA3-B045-1DFA50104289} Third party service
+YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           ServiceID = {aaaabbbb-0000-cccc-1111-dddd2222eeee} Third party service
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           Search Scope = {Current User}
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           Caller SID for Applicability: S-1-12-1-2933642503-1247987907-1399130510-4207851353
-YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            Got 855E8A7C-ECB4-4CA3-B045-1DFA50104289 redir Client/Server URL: https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx""
+YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            Got aaaabbbb-0000-cccc-1111-dddd2222eeee redir Client/Server URL: https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx""
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            Token Requested with 0 category IDs.
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            GetUserTickets: No user tickets found. Returning WU_E_NO_USERTOKEN.
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Method failed [AuthTicketHelper::GetDeviceTickets:570]
@@ -88,7 +88,7 @@ YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Method fai
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] GetAgentTokenFromServer
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] GetAgentToken
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] EP:Call to GetEndpointToken
-YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Failed to obtain service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 plugin Client/Server auth token of type 0x00000001
+YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Failed to obtain service aaaabbbb-0000-cccc-1111-dddd2222eeee plugin Client/Server auth token of type 0x00000001
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  ProtocolTalker  *FAILED* [80070426] Method failed [CAgentProtocolTalkerContext::DetermineServiceEndpoint:377]
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  ProtocolTalker  *FAILED* [80070426] Initialization failed for Protocol Talker Context
 YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           Exit code = 0x80070426
@@ -101,7 +101,7 @@ The 0x80070426 error code translates to:
 ERROR_SERVICE_NOT_ACTIVE - # The service has not been started.
 ```
 
-Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. The DCAT Flighting service (ServiceId: 855E8A7C-ECB4-4CA3-B045-1DFA50104289) relies on MSA to get the global device ID for the device. Without the MSA service running, the global device ID won't be generated and sent by the client and the search for feature updates never completes successfully.
+Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. The DCAT Flighting service (ServiceId: aaaabbbb-0000-cccc-1111-dddd2222eeee) relies on MSA to get the global device ID for the device. Without the MSA service running, the global device ID won't be generated and sent by the client and the search for feature updates never completes successfully.
 
 To resolve this issue, reset the MSA service to the default StartType of "manual."
 

support/windows-client/licensing-and-activation/activation-failures-not-genuine-notifications-volume-licensed-kms-client.md

@@ -1,6 +1,6 @@
 ---
 title: Activation failures around January 8, 2019, on volume-licensed Windows 7 Service Pack 1 KMS clients
-description: Provides a solution to an issue where users may receive the Windows Activation or (Windows is not genuine) notifications starting at or after 10:00 UTC, January 8, 2019.
+description: Provides a solution to an issue where users might receive the Windows Activation or (Windows is not genuine) notifications starting at or after 10:00 UTC, January 8, 2019.
 ms.date: 01/15/2025
 manager: dcscontentpm
 audience: itpro
@@ -14,14 +14,14 @@ appliesto:
 ---
 # Activation failures and (not genuine) notifications around January 8, 2019, on volume-licensed Windows 7 Service Pack 1 KMS clients
 
-This article provides a solution to an issue where users may receive the Windows Activation or "Windows is not genuine" notifications starting at or after 10:00 UTC, January 8, 2019.
+This article provides a solution to an issue where users might receive the Windows Activation or "Windows is not genuine" notifications starting at or after 10:00 UTC, January 8, 2019.
 
 _Applies to:_   Windows 7 Service Pack 1  
 _Original KB number:_   4487266
 
 ## Summary
 
-This article applies to volume-licensed Windows 7 Service Pack 1 devices that use Key Management Service (KMS) activation and have the [KB 971033](https://support.microsoft.com/help/971033) update installed. Some users may receive the Windows Activation or "Windows is not genuine" notifications starting at or after 10:00 UTC, January 8, 2019.
+This article applies to volume-licensed Windows 7 Service Pack 1 devices that use Key Management Service (KMS) activation and have the [KB 971033](https://support.microsoft.com/help/971033) update installed. Some users might receive the Windows Activation or "Windows is not genuine" notifications starting at or after 10:00 UTC, January 8, 2019.
 
 On January 9, 2019, we reverted a change that was made to Microsoft Activation and Validation servers. For devices that continue to report activation and "not genuine" notifications, you should remove [KB 971033](https://support.microsoft.com/help/971033) by following the steps in the [Resolution](#resolution) section.
 
@@ -34,11 +34,11 @@ Windows editions that support volume-licensing activation include the following:
 - Windows 7 Enterprise N
 - Windows 7 Enterprise E
 
-For Windows editions that experience activation and "not genuine" errors that are not caused by the Microsoft Activation and Validation server change around January 8, 2019, we recommend that you follow standard activation troubleshooting.
+For Windows editions that experience activation and "not genuine" errors that aren't caused by the Microsoft Activation and Validation server change around January 8, 2019, we recommend that you follow standard activation troubleshooting.
 
 ## Symptoms
 
-1. You receive a **Windows is not genuine** error message after you log on.
+1. You receive a **Windows is not genuine** error message after you sign in.
 
     :::image type="content" source="media/activation-failures-not-genuine-notifications-volume-licensed-kms-client/windows-is-not-genuine-error-message.png" alt-text="Screenshot of Windows is not genuine error message." border="false":::
 
@@ -60,7 +60,7 @@ For Windows editions that experience activation and "not genuine" errors that ar
 
 |Event log|Event source|Event ID|Description|
 |---|---|---|---|
-|Application|Microsoft-Windows-Security-SPP|8209|Genuine state set to non-genuine (0x00000000) for application Id 55c92734-d682-4d71-983e-d6ec3f16059f|
+|Application|Microsoft-Windows-Security-SPP|8209|Genuine state set to non-genuine (0x00000000) for application Id 00001111-aaaa-2222-bbbb-3333cccc4444|
 |Application|Microsoft-Windows-Security-SPP|8208|Acquisition of genuine ticket failed (hr=0xC004C4A2) for template Id 66c92734-d682-4d71-983e-d6ec3f16059f|
 |Application|Windows Activation Technologies|13|Genuine validation result: hrOffline = 0x00000000, hrOnline =0xC004C4A2|
 |Application|Microsoft-Windows-Security-SPP|8196|License Activation Scheduler (sppuinotify.dll) was not able to automatically activate. Error code:  0xC004F200:|
@@ -70,15 +70,15 @@ For Windows editions that experience activation and "not genuine" errors that ar
 A recent update to the Microsoft Activation and Validation unintentionally caused a "not genuine" error on volume-licensed Windows 7 clients that had [KB971033](https://support.microsoft.com/help/971033) installed. The change was introduced at 10:00:00 UTC on January 8, 2019, and was reverted at 4:30:00 UTC on January 9, 2019.
 
 > [!NOTE]
-> This timing coincides with the release of the "1B" January 2019 updates ([KB 4480960](https://support.microsoft.com/help/4480960) and [KB 4480970](https://support.microsoft.com/help/4480970)) that were released on Tuesday, January 8, 2019. These events are not related.
+> This timing coincides with the release of the "1B" January 2019 updates ([KB 4480960](https://support.microsoft.com/help/4480960) and [KB 4480970](https://support.microsoft.com/help/4480970)) that were released on Tuesday, January 8, 2019. These events aren't related.
 
-Windows 7 devices that have [KB971033](https://support.microsoft.com/help/971033) installed but did not experience this issue between the time of the change (10:00:00 UTC, January 8, 2019) and the time of the reversion of that change (4:30:00 UTC, January 9, 2019)  should not experience the issue that is described in this article.
+Windows 7 devices that have [KB971033](https://support.microsoft.com/help/971033) installed but didn't experience this issue between the time of the change (10:00:00 UTC, January 8, 2019) and the time of the reversion of that change (4:30:00 UTC, January 9, 2019) shouldn't experience the issue that this article describes.
 
 [KB971033](https://support.microsoft.com/help/971033) contains the following text:
 
 "Note For an Enterprise customer who uses Key Management Service (KMS) or Multiple Activation Key (MAK) volume activation, we generally recommend to NOT install this update in their reference image or already deployed computers. This update is targeted at consumer installs of Windows using RETAIL activation."
 
-We strongly recommend that you uninstall [KB971033](https://support.microsoft.com/help/971033) from all volume-licensed Windows 7-based devices. This includes devices that are not currently affected by the issue that is mentioned in the [Symptoms](#symptoms) section.
+We strongly recommend that you uninstall [KB971033](https://support.microsoft.com/help/971033) from all volume-licensed Windows 7-based devices. This includes devices that aren't currently affected by the issue that is mentioned in the [Symptoms](#symptoms) section.
 
 ## Resolution
 
@@ -153,7 +153,7 @@ The following table lists the KMS client keys for each edition of Windows 7.
 > [!NOTE]
 >
 > - Scripts that contain the KMS client setup key must target the corresponding operating system edition.
-> - For services that do not have [KB 971033](https://support.microsoft.com/help/971033) installed but experience the issue that is mentioned in the [Symptoms](#symptoms) section, you can also rebuild activation-related files and reactivate the system by using the script that is mentioned in the list of reactivation commands.
+> - For services that don't have [KB 971033](https://support.microsoft.com/help/971033) installed but experience the issue that is mentioned in the [Symptoms](#symptoms) section, you can also rebuild activation-related files and reactivate the system by using the script that is mentioned in the list of reactivation commands.
 
 ## Data collection
 

support/windows-client/windows-security/enforcing-bitlocker-policies-by-using-intune-known-issues.md

@@ -243,7 +243,7 @@ The policy deployment fails and the failure generates the following events in Ev
 > Event:
 > Failed to backup BitLocker Drive Encryption recovery information for volume C: to your Microsoft Entra ID.
 >
-> TraceId: {cbac2b6f-1434-4faa-a9c3-597b17c1dfa3}
+> TraceId: {0000aaaa-11bb-cccc-dd22-eeeeee333333}
 > Error: Unknown HResult Error code: 0x80072f9a
 
 > Event ID:778