Hi ​@Daiana Grimi,

You may refer to the below thread for an additional issue that can occur on Win11.

Automation Anywhere 360 Browser Extension Access Issue in Windows 11 Machine. | Community

Thanks ​@Padmakumar !😀

Apart from that, you may keep in mind the following points as well.

1. UI & Selector Changes

• Windows 11 introduces a redesigned UI with rounded corners, new iconography, and layout changes.
• Impact:
  • Bots using image-based automation or pixel matching may fail because the visual elements look different.
  • Bots relying on selectors (class names, automation IDs) can break if these properties have changed or render differently.
• Mitigation: Revalidate and update selectors after migration; prefer object-based automation over image-based.

   

2. DPI & Resolution Differences

• Windows 11 often defaults to higher DPI scaling (125% or 150%) on modern displays.
• Impact: Bots using absolute coordinates or image recognition may fail due to scaling differences.
• Mitigation: Standardize DPI settings (e.g., 100%) or use relative positioning in bots.

   

3. Application Version Changes

• Built-in apps like Notepad, Calculator, Edge have different versions and UI in Windows 11.
• Impact: Bots targeting these apps might fail if they depend on specific UI layouts.
• Mitigation: Validate all target applications and update automation logic if needed.

   

4. Bot Agent Folder Deletion

• During OS upgrade, the Automation Anywhere folder under System32\config\systemprofile\AppData\Local can be deleted.
• Impact: Bot Agent may fail to start after upgrade.
• Mitigation: Backup Bot Agent folders before upgrade and restore them afterward.

   

5. Browser Extension Issues

• On Windows 11, AA360 browser extensions (Chrome/Edge) can become locked or uneditable after Bot Agent installation.
• Impact: Web automation may fail.
• Fix: Disable automatic extension installation in Control Room before installing Bot Agent, then manually manage extensions.

   

6. Image Recognition Failures

• Certification tests showed image recognition failed on default Windows 11 desktop UI.
• Impact: Bots using image-based commands for desktop elements may not work.
• Mitigation: Switch to object-based automation or update image captures.

   

7. Device Registration & Connectivity

• If the machine name or hardware ID changes during migration, Control Room may treat it as a new device.
• Impact: Bots won’t run until the device is re-registered.
• Mitigation: Plan for device re-registration post-upgrade.

   

8. Compatibility Requirements

• Windows 11 support starts from Automation 360 v.26. Older Bot Agents will not work.
• Impact: If you’re on an older version, upgrade Control Room and Bot Agent first.