Skip to content

Commit 31cf8f5

Browse files
learn-build-service-prod[bot]learn-build-service-prod[bot]
authored
Merge pull request #10361 from MicrosoftDocs/main
Auto Publish – main to live - 2025-12-12 18:00 UTC
2 parents cdd9a64 + 64cbef5 commit 31cf8f5

6 files changed

Lines changed: 553 additions & 0 deletions

File tree

‎support/azure/virtual-machines/linux/linux-azure-guest-agent-tools-vmassist.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,7 @@ Go to the following GitHub location and follow the instructions there to [downlo
6464
If you open a support request, please include both of these files to aid the support agent who assists you.
6565

6666
## Known issues
67+
6768
- Don't try to run VM assist on appliances. Appliances don't run on general purpose operating systems, and the guest agent might not run at all.
6869
- Distributions outside PAYG versions of RedHat or SUSE, or any Ubuntu or Mariner or Azure Linux, might display false positive warnings about repository names. This situation requires a more careful reading because even official repositories might not match strict pattern matching. This condition is true because we don't build cases for all distributions.
6970
- Ubuntu 24.04 has a different architecture of the SSH service. It might flag the service even if the service is operating well.

‎support/power-platform/power-automate/desktop-flows/ui-automation/block-input-action-issues.md‎

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
title: Troubleshoot UI Automation Action Failures After a Block Input Action
3+
description: Resolves an issue in which UI or web automation actions fail after a Block Input action in Power Automate for desktop.
4+
ms.reviewer: iomimtso, nimoutzo, jspantouris, v-shaywood
5+
ms.date: 11/21/2025
6+
ms.custom: sap:Desktop flows\UI or browser automation
7+
---
8+
# UI automation actions fail after Block Input action
9+
10+
This article provides solutions for an issue in which UI or web automation actions that involve mouse or keyboard input don't work as expected after you use a **Block Input** action in Power Automate for desktop.
11+
12+
## Symptoms
13+
14+
When you run a desktop flow that includes a [Block Input](/power-automate/desktop-flows/actions-reference/mouseandkeyboard#blockinput) action by having the **Block It** parameter set to **True**, subsequent UI or web automation actions might not work as expected. The flow continues to the next actions without showing any errors, but the mouse or keyboard interactions aren't run.
15+
16+
The following actions might not work correctly after a **Block Input** action:
17+
18+
- Populate text field in window
19+
- Press button in window
20+
- Select radio button in window
21+
- Set checkbox state in window
22+
- Set drop-down list value in window
23+
- Click UI element in window
24+
- Select tab in window
25+
- Hover mouse over UI element in window
26+
- Click link on web page (if the **Send Physical Click** option is enabled)
27+
- Populate text field on web page (if the **Populate text using physical keystrokes** option is enabled)
28+
- Send keys
29+
30+
## Cause
31+
32+
The **Block Input** action requires elevated rights to run because of its critical functionality. If **Block Input** is active by having **Block It** set to **True**, the action can interfere with subsequent UI or web automation actions that require physical mouse or keyboard input.
33+
34+
> [!NOTE]
35+
> The **Block Input** action works only when you:
36+
>
37+
> - Run a desktop flow through the console or debug it through the designer.
38+
> - Run Power Automate for desktop runs by having elevated rights.
39+
>
40+
> For more information, see [Run Power Automate with elevated rights](/power-automate/desktop-flows/how-to/run-power-automate-elevated-rights).
41+
42+
## Solution 1: Don't use the Block Input action
43+
44+
To prevent this issue, design your flow without the **Block Input** action, if possible.
45+
46+
## Solution 2: Use alternative mouse and keyboard actions
47+
48+
If you have to use **Block Input** and perform mouse actions, use one of the following actions from the _Mouse and keyboard_ category instead of UI automation actions. For more information, see [Mouse and keyboard actions reference](/power-automate/desktop-flows/actions-reference/mouseandkeyboard).
49+
50+
### Alternative A: Use Move mouse and Send mouse click actions
51+
52+
1. Use the [Move mouse](/power-automate/desktop-flows/actions-reference/mouseandkeyboard?source=recommendations#movemouse) action to move the mouse pointer to a specific position.
53+
1. Use the [Send mouse click](/power-automate/desktop-flows/actions-reference/mouseandkeyboard?source=recommendations#sendmouseclick) action to perform the click.
54+
55+
The **Move mouse** action requires you to specify coordinates. Use the **Relative to** parameter to specify whether the new mouse position is relative to:
56+
57+
- **Current Mouse Position**
58+
- **Active Window** (the foremost window)
59+
- **Screen** (relative to the upper-left corner of the screen)
60+
61+
### Alternative B: Use Move mouse to Image action
62+
63+
Use the [Move mouse to Image](/power-automate/desktop-flows/actions-reference/mouseandkeyboard#movemousetoimagebase) action by having the **Send a click after moving mouse** option enabled. This action moves the mouse to the position of a specified image on the screen, and then sends a click.
64+
65+
### Alternative C: Use Move mouse to Text on Screen (OCR) action
66+
67+
Use the [Move mouse to Text on Screen (OCR)](/power-automate/desktop-flows/actions-reference/mouseandkeyboard#movemousetotextonscreenwithocraction) action by having the **Send a click after moving mouse** option enabled. This action uses optical character recognition (OCR) to locate text on the screen, moves the mouse to that position, and then sends a click.
68+
69+
### Solution 3: Temporarily disable Block Input
70+
71+
If you have to use **Block Input** but also have to perform actions that require physical input, use the following method:
72+
73+
1. If you need input blocked, use the **Block Input** action by having **Block It** set to **True**.
74+
1. Before you run a UI or web automation action that requires mouse or keyboard input, add a **Block Input** action that has **Block It** set to **False**.
75+
1. Run the UI or web automation action.
76+
1. If you still have to block input after the action runs, add another **Block Input** action that has **Block It** set to **True**.
77+
78+
This method lets you temporarily enable physical input for specific actions and also maintains input blocking for the rest of the flow.

‎support/power-platform/power-automate/toc.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -113,6 +113,8 @@ items:
113113
href: desktop-flows/ui-automation/ui-rdp-automation/rdp-no-highlight.md
114114
- name: '"The remote desktop was not found" error'
115115
href: desktop-flows/ui-automation/ui-rdp-automation/error-remote-desktop-not-found.md
116+
- name: UI automation actions fail after Block Input action
117+
href: desktop-flows/ui-automation/block-input-action-issues.md
116118
- name: UI element picker or recorder can't view UI elements in desktop applications
117119
href: desktop-flows/ui-automation/element-picker-cant-see-elements.md
118120
- name: UIPI issues with UI and web automation actions

‎support/windows-server/high-availability/troubleshoot-rolling-upgrades.md‎

Lines changed: 224 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,224 @@
1+
---
2+
title: Troubleshoot Rolling Upgrade Issues
3+
description: Discusses how to troubleshoot rolling upgrade issues.
4+
ms.date: 12/05/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.author: jeffhugh
9+
ms.reviewer: kaushika, v-ryanberg, v-gsitser
10+
ms.custom:
11+
- sap:rolling upgrade and high availability\rolling upgrade issues
12+
- pcy:WinComm Storage High Avail
13+
- appliesto:
14+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
15+
---
16+
# Troubleshoot rolling upgrade issues
17+
18+
## Summary
19+
20+
This article provides a structured troubleshooting method to resolve common issues that you might encounter during rolling upgrades in Windows Server Failover Clustering (WSFC), Storage Spaces Direct, SQL Server Always On availability groups, and Hyper-V.
21+
22+
Rolling upgrades are essential for maintaining and upgrading systems while experiencing minimal downtime. However, challenges such as compatibility and configuration errors can affect availability, and potentially cause data loss.
23+
24+
## Prerequisites
25+
26+
Before you start a rolling upgrade:
27+
28+
- Verify that the rolling upgrade feature is supported for your workload and operating system (OS) versions.
29+
- Verify that all cluster nodes are healthy by using the `Get-ClusterNode` PowerShell command.
30+
- Make sure that you have up-to-date backups, including:
31+
- System state
32+
- Cluster configuration
33+
- User data
34+
35+
## Potential workarounds
36+
37+
### Address rolling upgrade failures
38+
39+
1. Move core resources to another node by using Failover Cluster Manager or the `Move-ClusterGroup` PowerShell command.
40+
2. Migrate roles and resources off the node by using `Suspend-ClusterNode -Drain`.
41+
3. Check cluster logs for dependencies or errors that might block the operation.
42+
43+
## Troubleshooting checklist
44+
45+
1. **Review prerequisites**: Make sure that the environment meets all prerequisites that are mentioned in this article.
46+
47+
2. **Validate cluster status**: Resolve any validation warnings or errors by running `Test-Cluster`.
48+
- Verify the current cluster functional level by using `Get-Cluster | Select ClusterFunctionalLevel`.
49+
- Validate network connectivity among all nodes.
50+
51+
3. **Plan and sequence upgrades**: Document the sequence of node upgrades (one node at a time).
52+
- Move cluster roles (such as virtual machines (VMs), availability groups, or file shares) off the node that's being upgraded.
53+
- Update all nodes to the latest supported updates or hotfixes for the current OS.
54+
55+
4. **Communicate with stakeholders**: Inform stakeholders and schedule maintenance windows.
56+
- Notify monitoring teams in order to avoid unnecessary alerts.
57+
58+
5. **Ensure application awareness**: Verify application compatibility for workloads such as SQL Server, Hyper-V, or file services.
59+
- Inform application owners about planned upgrades.
60+
61+
6. **Conduct pre-upgrade tests**: Review logs for Windows, applications, clusters, and storage to identify any pre-existing issues.
62+
63+
## Common issues and their respective solutions
64+
65+
### 1. Rolling upgrade doesn't start or node can't be evicted
66+
67+
**Symptoms**
68+
69+
You can't pause, drain, or remove a node from the cluster. You receive error messages such as the following example:
70+
71+
> Node... cannot be removed from the cluster.
72+
73+
**Cause**
74+
75+
The node hosts core cluster resources, dependencies are misconfigured or the cluster is unstable.
76+
77+
**Solution**
78+
79+
1. Move core resources to another node by using Failover Cluster Manager or `Move-ClusterGroup`.
80+
2. move roles and resources by running `Suspend-ClusterNode -Drain`.
81+
3. Make sure that the node isn't the last up-to-date or quorum node.
82+
4. Check cluster logs for blocking dependencies.
83+
84+
### 2. Can't restore upgraded node to cluster
85+
86+
**Symptoms**
87+
88+
You receive a version mismatch message or error messages such as the following example:
89+
90+
> A node attempted to join a failover cluster but failed due to incompatibility.
91+
92+
**Cause**
93+
94+
Unsupported OS version mix or nonupdated node.
95+
96+
**Solution**
97+
98+
1. Verify the supported OS and cluster version matrix.
99+
2. Update the node to the latest cumulative update (CU).
100+
3. Upgrade the OS versions sequentially (for example, 2016 → 2019 → 2022).
101+
4. Identify versioning errors by using `Get-ClusterLog`.
102+
103+
### 3. Resource or service doesn't come online
104+
105+
**Symptoms**
106+
107+
Resources such as VMs or file shares enter a failed or offline state post-upgrade. Common Event IDs include `1069`, `1146`, and `1230`.
108+
109+
**Cause**
110+
111+
Misconfiguration during upgrade, missing registry keys or files, or service account failures.
112+
113+
**Solution**
114+
115+
1. Check cluster events in Failover Cluster Manager.
116+
2. Verify resource owner configurations by running `Get-ClusterResource | Get-ClusterOwnerNode`.
117+
3. Repair or re-create missing dependencies.
118+
4. Restart cluster services by running `Restart-Service ClusSvc`.
119+
120+
### 4. Quorum or communication loss
121+
122+
**Symptoms**
123+
124+
Cluster goes offline, nodes enter quarantine, or Event IDs `1135` and `1136` appear.
125+
126+
**Cause**
127+
128+
Network partition, firewall configuration, or quorum misconfiguration.
129+
130+
**Solution**
131+
132+
1. Make sure that all required ports are open.
133+
2. Check network, DNS, and routing configurations.
134+
3. Check quorum settings by running `Get-ClusterQuorum`. Update settings as appropriate.
135+
4. To identify root causes, run `Validate-Cluster`.
136+
137+
### 5. Update failure or known bug
138+
139+
**Symptoms**
140+
141+
Cluster services stop responding after an update, or resources fail because of a known problematic update.
142+
143+
**Cause**
144+
145+
Cluster instability occurred after a Microsoft update installation.
146+
147+
**Solution**
148+
149+
1. Review Microsoft Knowledge Base (KB) articles for known issues.
150+
2. Remove problematic updates, if it's necessary.
151+
3. Apply recommended hotfixes or wait for new updates.
152+
4. Open a support case if the issue remains unresolved.
153+
154+
### 6. Cluster validation or functional level errors
155+
156+
**Symptoms**
157+
158+
Can't update the cluster functional level, or validation fails.
159+
160+
**Cause**
161+
162+
Mixed OS versions, incomplete upgrades, or outdated drivers.
163+
164+
**Solution**
165+
166+
1. Update all nodes, and make sure that they're joined to the cluster.
167+
2. Update hardware drivers (such as network and storage) and firmware.
168+
3. Complete the upgrade by using `Update-ClusterFunctionalLevel`.
169+
4. Review logs for driver or validation failures.
170+
171+
## Advanced troubleshooting and data collection
172+
173+
For persistent or complex issues, collect the following data.
174+
175+
**Cluster logs**
176+
177+
```powershell
178+
179+
Get-ClusterLog -TimeSpan 24:00 -Destination
180+
181+
```
182+
183+
**System and application event logs**
184+
185+
```powershell
186+
187+
Get-WinEvent -LogName System -MaxEvents 1000 | Export-Csv <Path>\SystemLogs.csv
188+
Get-WinEvent -LogName Application -MaxEvents 1000 | Export-Csv <Path>\AppLogs.csv
189+
190+
```
191+
192+
**Resource and node status**
193+
194+
```powershell
195+
196+
197+
Get-ClusterNode
198+
Get-ClusterResource
199+
Get-ClusterGroup
200+
Test-Cluster
201+
202+
```
203+
204+
**Network and driver information**
205+
206+
```powershell
207+
208+
Get-NetAdapter -IncludeHidden | Export-Csv <Path>\NetAdapters.csv
209+
210+
```
211+
212+
**Update history**
213+
214+
```powershell
215+
216+
Get-HotFix | Export-Csv \Hotfix.csv
217+
218+
```
219+
220+
## References
221+
222+
- [Upgrade a Windows Server failover cluster with a cluster OS rolling upgrade](/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade)
223+
- [Update-ClusterFunctionalLevel](/powershell/module/failoverclusters/update-clusterfunctionallevel)
224+
- [Known issues - KB5062557](https://support.microsoft.com/help/5062557)

0 commit comments

Comments
 (0)