Merge pull request #9102 from sevend2/KeepASIS6177

AB#6177: Update ms.data for keep as is articles

Author: sevend2

support/windows/win32/addin-components-core-os-processes.md

@@ -1,10 +1,9 @@
 ---
 title: Add-in component guidelines for core OS processes
 description: Avoid using high-level languages, libraries, or frameworks when building add-in components loaded by system processes.
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ms.custom: sap:Security Development\Other
 ms.reviewer: davean, v-jayaramanp
-ms.topic: troubleshooting
 ---
 
 # Add-in component guidelines for core OS processes

support/windows/win32/cannot-start-transaction-ms-dtc.md

@@ -1,7 +1,7 @@
 ---
 title: Can't start a transaction in MS DTC
 description: This article describes a problem that may occur intermittently when you try to start a transaction in the MS DTC. A resolution is provided.
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ms.custom: sap:Distributed Transactions\DTC programming and runtime
 ---
 

support/windows/win32/client-application-error-create-com-plus-component.md

@@ -1,7 +1,7 @@
 ---
 title: An application fails to create a COM+ component
 description: This article describes a problem that might occur when a client application tries to create a COM+ component, and the client application receives an error message.
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ms.custom: sap:Component Development\COM, DCOM, and COM+ Programming and Runtime
 ms.reviewer: wmascia
 ---
@@ -37,10 +37,10 @@ This problem occurs because the Component Object Model (COM) initialization coun
 
 ## Resolution
 
-To resolve this problem, remove the `CoInitialize` calls and the `CoUninitialize` calls from the affected COM DLL. A COM DLL that exposes COM components and is loaded through COM calls from a client should not call the `CoInitialize` function or the `CoUninitialize` function on any thread that is used to load or to start the DLL. These threads are owned by the client application, by the COM runtime, or by the COM+ runtime. Only the COM DLL should call these APIs on additional threads that were explicitly created by the COM DLL. However, it is a common bug for COM DLLs to call the `CoInitialize` function and the `CoUninitialize` function in response to attach events and detach events in the `DllMain` function.
+To resolve this problem, remove the `CoInitialize` calls and the `CoUninitialize` calls from the affected COM DLL. A COM DLL that exposes COM components and is loaded through COM calls from a client shouldn't call the `CoInitialize` function or the `CoUninitialize` function on any thread that is used to load or to start the DLL. These threads are owned by the client application, by the COM runtime, or by the COM+ runtime. Only the COM DLL should call these APIs on additional threads that were explicitly created by the COM DLL. However, it's a common bug for COM DLLs to call the `CoInitialize` function and the `CoUninitialize` function in response to attach events and detach events in the `DllMain` function.
 
 > [!NOTE]  
-> It is correct for a standard Win32 DLL that isn't loaded through COM to call these APIs if the standard Win32 DLL plans to use COM APIs. However, these functions should not be called from the `DllMain` function.
+> It's correct for a standard Win32 DLL that isn't loaded through COM to call these APIs if the standard Win32 DLL plans to use COM APIs. However, these functions shouldn't be called from the `DllMain` function.
 
 For more information about the `CoInitialize` function, see [CoInitialize function](/windows/win32/api/objbase/nf-objbase-coinitialize).
 
@@ -56,24 +56,24 @@ To determine which COM component contains the affected code, use the Microsoft I
 1. [Download and install DebugDiag](https://www.microsoft.com/download/details.aspx?id=58210).
 2. Create a crash rule in DebugDiag. To do this, follow these steps:
 
-   1. Click **Start**, point to **Programs**, point to **IIS Diagnostics (32bit)**, point to **Debug Diagnostics Tool**, and then click **Debug Diagnostics Tool 1.0**.
-   2. If the **Select Rule Type** dialog box opens, click **Cancel**.
-   3. On the **Tools** menu, click **Options And Settings**.
-   4. Click the **Folders and Search Paths** tab, and then enter `srv*C:\symsrv\*http://msdl.microsoft.com/download/symbols` in the **Symbol Search Path For Analysis** field.
-   5. In the **Symbol Search Path For Debugging** field, enter `srv*C:\symsrv\*http://msdl.microsoft.com/download/symbols`, and then click **OK**.
-   6. Click **Add Rule**.
-   7. Click **Crash**, and then click **Next**.
-   8. Click **A specific MTS/COM+ application (included high and medium isolation websites)**, and then click **Next**.
-   9. Click the appropriate COM+ application, and then click **Next**.
-   10. In the **Advanced Configuration (Optional)** dialog box, click **Breakpoints**.
-   11. In the **Configure Breakpoints** dialog box, click **Add Breakpoint**.
-   12. In the **Configure Breakpoint** dialog box, enter *ole32!CoInitializeEx* in the **Breakpoint Expression** field, enter *1000* in the **Action Type** field, keep **Log Stack Trace** in the **Action Type** field, and then click **OK**.
-   13. In the **Configure Breakpoints** dialog box, click **Add Breakpoint**.
-   14. In the **Configure Breakpoint** dialog box, enter *ole32!CoUninitialize* in the **Breakpoint Expression** field, enter *1000* in the **Action Limit** field, and then click **OK**.
-   15. In the **Configure Breakpoints** dialog box, click **Save & Close**.
-   16. In the **Advanced Configuration (Optional)** dialog box, click **Next**.
-   17. In the **Select Dump Location And Rule Name (Optional)** dialog box, click **Next**.
-   18. In the **Rule Completed** dialog box, click **Activate the rule now**, and then click **Finish**.
+   1. Select **Start**, point to **Programs**, point to **IIS Diagnostics (32bit)**, point to **Debug Diagnostics Tool**, and then select **Debug Diagnostics Tool 1.0**.
+   2. If the **Select Rule Type** dialog box opens, select **Cancel**.
+   3. On the **Tools** menu, select **Options And Settings**.
+   4. Select the **Folders and Search Paths** tab, and then enter `srv*C:\symsrv\*http://msdl.microsoft.com/download/symbols` in the **Symbol Search Path For Analysis** field.
+   5. In the **Symbol Search Path For Debugging** field, enter `srv*C:\symsrv\*http://msdl.microsoft.com/download/symbols`, and then select **OK**.
+   6. Select **Add Rule**.
+   7. Select **Crash**, and then select **Next**.
+   8. Select **A specific MTS/COM+ application (included high and medium isolation websites)**, and then select **Next**.
+   9. Select the appropriate COM+ application, and then select **Next**.
+   10. In the **Advanced Configuration (Optional)** dialog box, select **Breakpoints**.
+   11. In the **Configure Breakpoints** dialog box, select **Add Breakpoint**.
+   12. In the **Configure Breakpoint** dialog box, enter *ole32!CoInitializeEx* in the **Breakpoint Expression** field, enter *1000* in the **Action Type** field, keep **Log Stack Trace** in the **Action Type** field, and then select **OK**.
+   13. In the **Configure Breakpoints** dialog box, select **Add Breakpoint**.
+   14. In the **Configure Breakpoint** dialog box, enter *ole32!CoUninitialize* in the **Breakpoint Expression** field, enter *1000* in the **Action Limit** field, and then select **OK**.
+   15. In the **Configure Breakpoints** dialog box, select **Save & Close**.
+   16. In the **Advanced Configuration (Optional)** dialog box, select **Next**.
+   17. In the **Select Dump Location And Rule Name (Optional)** dialog box, select **Next**.
+   18. In the **Rule Completed** dialog box, select **Activate the rule now**, and then select **Finish**.
 
 DebugDiag monitors the selected COM+ application when the application runs. Every time that DebugDiag experiences one of the selected breakpoints, DebugDiag adds data to a log file. By default, the log file will be named:  
 `C:\Program Files\IIS Resources\DebugDiag\Logs\dllhost__PID__\<pid>\__Date__\<date> __Time\_\<time> Log.txt`

support/windows/win32/coinitializeex-fails-after-calling-htmlhelp-same-thread.md

@@ -1,25 +1,25 @@
 ---
 title: CoInitializeEx fails after calling HtmlHelp on the same thread
 description: Provides a workaround for an issue where the CoInitializeEx function fails after calling the HtmlHelp function on the same thread.
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ms.reviewer: v-sidong
 author: hihayak
 ms.author: hihayak
 ms.custom: sap:Component Development\COM, DCOM, and COM+ Programming and Runtime
 ---
 # CoInitializeEx function fails after calling the HtmlHelp function on the same thread
 
-This article discusses an issue where the [CoInitializeEx function](/windows/win32/api/combaseapi/nf-combaseapi-coinitializeex) fails after calling the `HtmlHelp` function on the same thread.
+This article discusses an issue where the [CoInitializeEx](/windows/win32/api/combaseapi/nf-combaseapi-coinitializeex) function fails after calling the `HtmlHelp` function on the same thread.
 
 _Applies to:_   All supported operating system
 
 ## Symptoms
 
-If an application calls `HtmlHelp` before calling `CoInitializeEx` with the specified `COINIT_MULTITHREADED` value, `CoInitializeEx` can return `RPC_E_CHANGED_MODE (0x80010106)`. As a result, the application may crash, hang, or display unexpected behavior.
+If an application calls `HtmlHelp` before calling `CoInitializeEx` with the specified `COINIT_MULTITHREADED` value, `CoInitializeEx` can return `RPC_E_CHANGED_MODE (0x80010106)`. As a result, the application might crash, hang, or display unexpected behavior.
 
 ## Cause
 
-If a thread that calls `HtmlHelp` hasn't been initialized with `CoInitialize` or `CoInitializeEx`, `HtmlHelp` initializes the thread as apartment-threaded with `COINIT_APARTMENTTHREADED`.
+If a thread that calls `HtmlHelp` isn't initialized with `CoInitialize` or `CoInitializeEx`, `HtmlHelp` initializes the thread as apartment-threaded with `COINIT_APARTMENTTHREADED`.
 
 ## Workaround
 

support/windows/win32/com-supports-collect-dump-file.md

@@ -1,7 +1,7 @@
 ---
 title: COM+ supports collection of dump file and process termination
 description: This article introduces the new functionalities of Microsoft COM+, including automatic collection of process dump file and process termination.
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ms.custom: sap:Component Development\COM, DCOM, and COM+ Programming and Runtime
 ms.reviewer: dave.anderson
 ---

support/windows/win32/common-dialog-box-not-display-folder-names.md

@@ -1,7 +1,7 @@
 ---
 title: Explorer-style common file dialog box doesn't display folder names
 description: Describes an issue that the Explorer-style common file dialog box doesn't display folder names longer than 67 characters.
-ms.date: 04/09/2024
+ms.date: 06/11/2025
 ms.custom: sap:Desktop app UI development\Windows controls and common dialogs
 ms.reviewer: karywa, davean, v-sidong
 ---

support/windows/win32/converting-pdf-file-to-bitmap-image.md

@@ -1,9 +1,9 @@
 ---
 title: Converting PDF to bitmap causes partial data loss in the image
 description: This article helps you resolve the problem of partial data loss when you convert a PDF to a Bitmap image by using the classes of the Windows.Data.Pdf namespace.
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ms.custom: sap:Graphics and Multimedia development\Printing and the Print Spooler API
-ms.reviewer: hiroakii, v-jayaramanp
+ms.reviewer: hihayak, v-jayaramanp
 ---
 
 # Converting PDF to bitmap causes partial data loss in the image

support/windows/win32/createprocesswithlogonw-fails-microsoft-entra-id-account.md

@@ -5,7 +5,7 @@ author: cts-davean
 ms.author: davean
 ms.reviewer: mihayash, v-sidong
 ms.custom: sap:System Services Development\Process, thread, and DLL APIs
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ---
 
 # CreateProcessWithLogonW fails when called on a Microsoft Entra account

support/windows/win32/enable-diagnostic-tracing-ms-dtc.md

@@ -1,7 +1,7 @@
 ---
 title: Enable diagnostic tracing for MS DTC
 description: This article describes how to enable diagnostic tracing for MS DTC on a Windows 10 computer.
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ms.reviewer: johngil
 ms.custom: sap:Distributed Transactions\DTC programming and runtime
 ms.topic: how-to

support/windows/win32/finger3or4-touch-interaction-no-longer-works.md

@@ -1,7 +1,7 @@
 ---
 title: Three-finger and four-finger touch interactions don’t work in Windows apps
 description: In Windows 11, some three-finger and four-finger interactions are no longer usable by applications.
-ms.date: 12/19/2023
+ms.date: 06/11/2025
 ms.custom: sap:Desktop app UI development\User interaction (keyboard, mouse, pen and touch)
 ms.reviewer: kybeck
 ---