Factors impacting Bot Runner devices after Windows 11 update

When you update to Windows 11, existing automations might be impacted in several areas due to changes in the design and architecture of the operating system. Review these details to understand the potential areas of impact.

Prerequisite

Before you update the operating system of the Bot Runner device to Windows 11, ensure that you completely back up all the Bot Agent related data, such as Bot Agent folder from Program Files\Automation Anywhere. Review the following instructions to back up the Bot Agent data:
  1. Ensure that you set the Bot Agent service to Stopped and Manual mode from the Windows Task Manager in the Bot Runner device.
  2. Back up Bot Agent folder from C:\Program Files\Automation Anywhere and Automation Anywhere folder from the following location: C:\Windows\System32\config\systemprofile\AppData\Local
    Note: After the update to Windows 11, the Automation Anywhere folder might be deleted. This folder contains the Bot Agent system files. Therefore, backing up the Automation Anywhere folder along with the Bot Agent folder ensures that your existing Bot Agent system files are retained.
  3. After updating to Windows 11, paste the Automation Anywhere folder that you had backed up in the following location: C:\Windows\System32\config\systemprofile\AppData\Local
  4. From Windows Task Manager in the Bot Runner device, start the Bot Agent service and set the status to Automatic.

Image-based automations

Image automation might be impacted by an update to Windows 11 if there are specific changes in the appearance of the application screens.

Here are a few factors to consider:

  • New user interface (UI) design
    • The interface in Windows 11 has rounded corners, changed iconography, and new layouts, which might cause issues for automation tools that rely on UI element recognition.
    • Tools that use selectors to identify controls by properties (such as class names and automation IDs) can fail if these properties have changed or are rendered differently.
  • High dots per inch (DPI) scaling and resolution
    • Windows 11 can have different default resolution or scaling settings, potentially changing the appearance of UI elements.

      This can impact image-based automations relying on pixel-perfect recognition.

    • Changes in resolution or DPI settings in Windows 11 might affect how UI elements are rendered.

      This might potentially cause recognition issues or misalignment of elements in image-based or pixel-based automation.

Keystroke-based automations

Keyboard automations might be impacted by a Windows 11 update. However, it is not likely that an automation might completely break, unless there are specific changes in keyboard shortcuts or application behavior.

Here are a few factors to consider:
  • New or altered shortcuts

    Windows 11 introduces new features such as snap layouts, virtual desktops, and enhanced multitasking, some of which include new or altered keyboard shortcuts. If your automation relies on sending key combinations, such as Win + A for the Action Center), any change in these mappings can affect the automation.

    For example, Windows 11 has added Win + Z for snap layouts, and shortcuts might behave differently in some applications.

  • Different behavior in applications

    Windows applications in Windows 11 might respond to keyboard input differently due to changes in the UI design or system interactions.

    For example, if the layout of a system dialog changes, automations that use the tab or arrow keys to navigate might not function as expected.

  • Native application changes

    Some native applications in Windows 11 (such as File Explorer and Settings) might have different layouts that can impact automations using specific key sequences (such as Alt + F for File menus).

    For example, if the File Explorer in Windows 11 is updated, it might alter how keyboard-based automations interact with it.

  • Language and region settings

    If Windows 11 changes language or keyboard region settings, it might impact automations that assume a specific keyboard layout.

    For example, using @ vs. " depending on the keyboard locale, which might occur during an update where settings might be altered.

  • UI responsiveness

    Windows 11 might alter the performance of certain applications or dialogs.

    Automations that send key inputs based on specific timing or assume certain delays might fail if the system responds faster or slower than expected. Adjusting the timing in your automation scripts might be required to ensure they work correctly.

  • Taskbar shortcuts

    In Windows 11, the taskbar is moved to the center, so some of the taskbar-related keyboard shortcuts (such as switching between apps with Win + number keys) might not behave exactly the same. This can affect automations that rely on managing taskbar positions.

  • Virtual desktop shortcuts

    Windows 11 enhances the virtual desktop experience with new keyboard shortcuts such as Win + Tab and Win + Ctrl + arrow keys.

    Automation scripts interacting with virtual desktops might be affected if these shortcuts are used or if the virtual desktop behavior changes.

  • Modifier key behavior

    Although not very likely, automation scripts sending combinations of modifier keys (Ctrl, Alt, Shift, Win) might encounter issues if any behavior related to these keys is modified in Windows 11.

  • Hotkey reassignments

    Some Windows 11 features might use different keyboard shortcuts or have redefined hotkey combinations, and these can affect automations that rely on sending keyboard inputs.

Mouse location based automations

Windows 11 has repositioned certain elements in menus and system dialogs, which might impact automations that depend on absolute mouse positions or hard-coded coordinates.

Here are a few factors to consider:
  • UI and element layout changes

    Windows 11 introduces a redesigned interface with new control placements, which can affect automations that rely on absolute or relative mouse coordinates.

    For example, elements such as buttons, icons, or menus might have moved or be resized, which can cause mouse clicks to miss their intended targets.

  • Taskbar and start menu

    The centered taskbar and restructured Start menu can affect mouse-based automations if the position of these elements is hard-coded.

  • Window control elements

    Elements such as title bars, buttons, and menus can have different placements or even names, requiring updates to automation selectors or identifiers.

  • Context menu changes

    Windows 11 has streamlined context menus, hiding some actions with the Show more options menu item.

    This change might disrupt automations depending on right-click menus or context-specific actions.

Recorder or object property based automations

When updating to Windows 11, recorder and object property-based automations that rely on UI elements or object paths might be affected due to changes in the way these UI elements are rendered or identified.

The following is a summary of how the update can impact such automations:
  • UI element properties
    • Windows 11 introduces a new UI design with modified layouts, and look and feel. These visual changes might alter element properties such as class names, control types, automation IDs, and accessibility labels.
    • Properties such as Automation ID or Control Type used by automation tools to recognize UI elements might change, causing selectors to fail.
    • Automations that rely on static object properties might fail to locate elements correctly, resulting in broken workflows.
  • Microsoft Internet Explorer and Edge browsers

    Microsoft Edge is more integrated with Windows 11, and Internet Explorer is deprecated. Browser-based automation scripts relying on Internet Explorermight have to be transitioned to Microsoft Edge or other supported browsers.

  • XPath and CSS selectors
    • If your automations rely on XPath or CSS Selectors for web-based application automations, changes in the UI hierarchy (DOM structure) can lead to incorrect element identification.
    • The positioning or parent-child relationship of elements within the DOM structure might change in Windows 11 applications. This can render previously valid XPaths or selectors as invalid. Automation relying on these paths for dynamic object identification might break due to path changes.
    • XPath-based identification for web pages can also be affected due to changes in default system browsers.
  • Element hierarchy and accessibility tree

    Windows 11 might change the hierarchy of UI elements in the accessibility tree, which is used by some automation tools for element identification.

    Parent-child relationships between elements might be altered, which can affect the element recognition logic used by recorders and UI frameworks. Tools that navigate the element hierarchy might fail to interact with the correct objects.

  • New control layouts

    The placement and arrangement of controls in Windows 11 applications might differ from those in Windows 10, particularly for system windows and redesigned applications.

    Object properties such as position or size used in automations might become inaccurate due to the new layout. Recorder-based automations that rely on object placement or control properties might require updates to account for changes in control layouts and properties.

  • Control types and frameworks

    New or updated UI frameworks (such as UWP and WinUI) might be adopted in Windows 11 applications, introducing new control types or altering how existing controls are rendered.

    Automations relying on identifying specific control types (such as buttons and text fields) might fail if the underlying framework changes the way these controls are represented in the automation tool.

  • Pre-recorded objects changes

    Recorder tool might capture different element properties and paths in Windows 11 (compared to Windows 10), due to changes in the object hierarchy or properties.

    Previously recorded sequences of interactions might require a re-recording or adjustment, especially if the UI changes significantly. New paths or properties captured by the recorder tool must be validated and tested.

File or folder path based automations

  • File Explorer redesign

    The File Explorer in Windows 11 has been updated, which might affect automations that interact with specific folders or rely on certain menus and context actions within the File Explorer.

  • Changes in default folder paths

    Windows 11 might have updated file system paths for certain applications, particularly for user-related folders (such as Documents and Downloads). If your automations rely on default Windows paths, they might be affected if any of these default locations are altered.

Window title based automations

Some Windows 11 applications might have different window titles, application identifiers, or metadata. Automations relying on window title matching (such as for focusing on a particular application or dialog) might not work correctly if titles change.

Application window title changes

Some applications and system dialogs might have different titles or metadata in Windows 11. Automations that rely on exact window titles to identify and interact with applications (such as using Find Window actions) might fail if titles change or new windows have different identifiers.

Other changes impacting existing automations

  • Stricter security policies

    Windows 11 includes enhanced security features such as Secure Boot and Trusted Platform Module (TPM). This might restrict certain automation operations, especially those that require administrative privileges, access to protected folders, or interaction with secure applications.

  • UAC and system dialog changes

    Changes in User Access Control (UAC) dialogs or security prompts might interfere with automations that attempt to interact with system-level processes. Some automations might be blocked or require changes to permissions and access settings.

  • Taskbar changes

    The centered taskbar and redesigned system tray in Windows 11 might break automations that rely on interacting with specific system tray icons or taskbar items by position.

  • System dialogs

    Changes to system dialogs, such as the Start menu or system notifications, can affect automations that rely on interacting with these elements.

  • CPU/GPU optimizations

    Windows 11 has improved optimizations for specific hardware that might impact the performance of automation processes, especially those that require high resource usage or interact with resource-heavy applications.

  • Multitasking and snap features

    Windows 11 introduces new multitasking and window snapping features (such as snap layouts), which can alter how windows are managed and that can impact automations that rely on managing multiple open windows.