Skip to content

Commit 984d90d

Browse files
authored
Merge pull request #8057 from MicrosoftDocs/users/johndund/updateinstalldocs
AB#3533: Update logs documentation to be more generic
2 parents 7f1a241 + c8681fc commit 984d90d

2 files changed

Lines changed: 21 additions & 23 deletions

File tree

Lines changed: 19 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,54 +1,52 @@
11
---
2-
title: Power Automate for desktop installation logs
3-
description: Introduces the locations that contain Power Automate for desktop installation logs.
4-
ms.reviewer: quseleba, guco
5-
ms.date: 09/13/2024
2+
title: Power Automate for desktop logs
3+
description: Introduces the locations that contain Power Automate for desktop logs.
4+
ms.reviewer: quseleba, guco, madiazor, johndund
5+
ms.date: 01/22/2025
66
ms.custom: sap:Desktop flows\Working with Power Automate for desktop
77
---
8-
# Power Automate for desktop installation logs
8+
# Power Automate for desktop logs
99

10-
If your Power Automate for desktop installation fails, you can use the logs described in this article to diagnose and resolve issues. If you need to contact [Microsoft Support](https://www.microsoft.com/power-platform/products/power-automate/support) for assistance with installation issues, collect the following logs in a .zip file and include them in the support request to expedite the investigation.
10+
When troubleshooting issues with Power Automate for desktop, you might need to collect logs for customer support to analyze. These logs can be for a failed installation, problems running desktop flows, or issues with Power Automate or the machine runtime application.
1111

1212
_Applies to:_   Power Automate
1313
_Original KB number:_   4555577
1414

1515
## Installer logs
1616

17-
These logs can be found in the _%temp%_ folder of the user who performed the installation. You can find them by typing _%temp%_ in the address bar of File Explorer. The files of interest are:
17+
The easiest way to get installer logs is to export them using the link provided at the end of a failed installation. When your installation fails and displays "There's a problem installing," select the **installation log files** link located under the **Troubleshooting tips** section.
18+
19+
:::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/installation-log-files.png" alt-text="Screenshot of the page that contains the installation log files link that you can use to export the installer logs.":::
20+
21+
If you need to get the installer files manually, they can be found in the _%temp%_ folder of the user who performed the installation. You can find them by typing _%temp%_ in the address bar of File Explorer to locate the following files:
1822

1923
- _Power Automate for desktop\_*.log_
2024
- _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_
2125

22-
The _Power Automate for desktop\_*.log_ file contains the general reason why the installation failed. The _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_ file has more detailed information.
26+
The _Power Automate for desktop\_*.log_ file contains the general reason for the installation failure. The _Power Automate for desktop\_\*\_\*\_MicrosoftFlowRPA.log_ file provides more detailed information.
2327

2428
:::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/power-automate-installer-logs.png" alt-text="Screenshot of the Power automate for desktop installer logs.":::
2529

26-
### How to export the Installer logs
30+
## On-premises product logs
2731

28-
If your installation encounters an error and displays the message "There's a problem installing," you can find more details by selecting the "installation log files" link located under the **Troubleshooting tips** section. This will allow you to export the installer logs.
32+
For issues with creating flows, [using the Runtime Application to register](/power-automate/desktop-flows/manage-machines#register-a-new-machine) or configure your machine, or issues during cloud runtime, you might need to gather on-premises logs.
2933

30-
:::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/installation-log-files.png" alt-text="Screenshot of the page that contains the installation log files link that you can use to export the installer logs.":::
34+
The easiest way to do this is to use the Power Automate machine runtime application. If you have the application installed, you can [use it to export logs automatically](/power-automate/desktop-flows/troubleshoot#collect-machine-logs).
3135

32-
## Program data logs
33-
34-
These are logs of the components installed on your machine. You can find them by typing the path _%programdata%\Microsoft\Power Automate\Logs_ in the address bar of File Explorer.
36+
If you need to collect on-premises logs manually, they can be found in _%programdata%\Microsoft\Power Automate\Logs_.
3537

3638
> [!NOTE]
3739
> You need administrator privileges to read or copy these files to another folder. After copying them to a different folder, non-administrator users can open them.
3840
3941
## Event Viewer logs
4042

41-
These logs are helpful when a Windows service fails to start.
43+
Event Viewer application logs are helpful when an application crashes or a Windows service fails to start.
4244

4345
Follow these steps to view and save the logs:
4446

4547
1. Open the Windows Event Viewer.
46-
2. Go to **Windows Logs** > **Application**, find the error, and review the information in the **General** and **Details** tabs.
47-
3. If needed, use the **Filter Current Log** menu to filter by **Event level** or **Logged** time (such as the last hour).
48+
2. Go to **Windows Logs** > **Application**, and look for an error with the source corresponding to the application that experienced the problem.
49+
3. Use the **Filter Current Log** menu to filter by **Event level** or **Logged** time (such as the last hour) if needed.
4850
4. To save the filtered log file, select **Save Filtered Log File As** and save it as an event file.
4951

5052
:::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/power-automate-event-viewer-logs.png" alt-text="Screenshot of an example error logged in the Event Viewer.":::
51-
52-
## More information
53-
54-
[Troubleshoot installation issues in Power Automate for desktop](power-automate-desktop-installation-issues.md)

support/power-platform/power-automate/desktop-flows/power-automate-desktop-installation-issues.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Installation issues in Power Automate for desktop
33
description: Helps troubleshoot stallation issues in Power Automate for desktop.
44
ms.reviewer: guco, johndund
5-
ms.date: 09/12/2024
5+
ms.date: 01/20/2025
66
ms.custom: sap:Desktop flows\Installation issues
77
---
88
# Troubleshoot installation issues in Power Automate for desktop
@@ -29,7 +29,7 @@ For a complete list of prerequisites, see [Prerequisites and limitations](/power
2929

3030
## Gather diagnostic information
3131

32-
Installation logs can provide useful details about the installation and help you diagnose and fix issues. For more information about where to find the logs, see [Power Automate for desktop installation logs](how-to-get-power-automate-desktop-installer-logs.md).
32+
Installation logs can provide useful details about the installation and help you diagnose and fix issues. For more information about where to find the logs, see [Power Automate for desktop installation logs](how-to-get-power-automate-desktop-installer-logs.md#installer-logs).
3333

3434
## Known issues and workarounds
3535

0 commit comments

Comments
 (0)