Collecting Softdrive Logs Using the Softdrive Log Collector Script

This article explains how to collect Softdrive-related logs using the Softdrive Log Collector PowerShell script.

The script helps collect logs needed by Softdrive Support when troubleshooting connection issues, display problems, Microsoft Teams issues, FSLogix profile issues, Windows errors, and other Softdrive-related behavior.

Use this link to download the script:

The script can be run from either:

• The Softdrive machine / VDI server
• The local machine / VDI client

When the script is launched, it will ask which timeframe should be collected and whether it is being run from the local machine or the Softdrive machine.

The final compressed ZIP file is saved to:

C:\Users\Public\Downloads

Applies To

• Softdrive Launcher
• Softdrive Windows machines
• Softdrive local client devices
• Windows 10
• Windows 11
• FSLogix environments
• Microsoft Teams troubleshooting

Prerequisites

Before running the script, make sure:

• You are signed in to the Windows machine where the logs need to be collected.
• You have downloaded the Softdrive Log Collector script.
• You can open PowerShell as Administrator.
• The user has recently reproduced the issue, if possible.

Download the script here:

SoftdriveLogCollector.ps1 

What Logs Are Collected?

The logs collected depend on where the script is being run.

Option 1: Running the Script on the Softdrive Machine / VDI Server

Use this option when you are connected inside the Softdrive desktop and need to collect logs from the Softdrive machine itself.

When this option is selected, the script collects items such as:

• Windows Event Logs
  • Application
  • Setup
  • System
• Softdrive server logs
• Softdrive temporary logs
• FSLogix event logs
• FSLogix file-based logs
• Microsoft Teams logs, when available

This option is useful when troubleshooting issues inside the Softdrive session, such as:

• FSLogix profile issues
• Login or profile loading problems
• Microsoft Teams problems inside the VDI
• Windows errors inside the Softdrive machine
• Application or system crashes inside the Softdrive machine

Option 2: Running the Script on the Local Machine / VDI Client

Use this option when you need to collect logs from the user’s physical/local computer, which is the machine used to connect to Softdrive.

When this option is selected, the script collects:

• Windows Event Logs
  • Application
  • Setup
  • System
• Softdrive client logs, usually located under:

C:\Users\<your-username>\AppData\Local\Programs\softdrive-launcher\<session>\temp\client

• Softdrive launcher logs, usually located under:

C:\Users\<your-username>\AppData\Roaming\softdrive-launcher\logs

This option is useful when troubleshooting issues related to the local device, such as:

• Softdrive Launcher failing to open
• Connection failures before reaching the VDI
• Local display, codec, or streaming behavior
• Local camera, microphone, or device redirection issues
• Softdrive client-side disconnects

Procedure

Step 1: Download the Script

Download the script to the user’s computer.

Recommended location:

C:\Users\<your-username>\Downloads

The script name is:

SoftdriveLogCollector.ps1

Step 2: Open PowerShell as Administrator

1. Click Start.
2. Type PowerShell.
3. Right-click Windows PowerShell.
4. Select Run as administrator.

Step 3: Go to the Downloads Folder

In the PowerShell window, run:

cd "$env:USERPROFILE\Downloads"

Step 4: Allow the Script to Run for This PowerShell Session

Run:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

If prompted to confirm the change, type:

A

Then press Enter.

Step 5: Run the Script

Run:

.\SoftdriveLogCollector.ps1

If the file name is different because it was downloaded more than once, check the exact name by running:

dir "$env:USERPROFILE\Downloads\*.ps1"

Then run the script using the exact file name shown.

Script Prompts

After launching, the script will ask for the timeframe.

Select one of the following options:

1) Last 12 hours
2) Last 7 days
3) Last 30 days

Then the script will ask where it is being run.

Select one of the following options:

1) Local machine / VDI client
2) Softdrive machine / VDI server

Choose the option that matches the machine where the script is currently running.

Expected Result

After the script finishes, it creates a compressed ZIP file containing the collected logs.

The ZIP file is saved in:

C:\Users\Public\Downloads

Send this ZIP file to Softdrive Support for review.

Troubleshooting

PowerShell says the script is not recognized

This usually means PowerShell cannot find the script in the current folder.

Confirm the script is in the Downloads folder:

dir "$env:USERPROFILE\Downloads\*.ps1"

Then run the script using the exact file name shown.

The script does not run because execution is disabled

Run the following command first:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

Then run the script again.

The ZIP file was not created

Check the following location:

C:\Users\Public\Downloads

If the ZIP file is not there, confirm that PowerShell was opened as Administrator and run the script again.

Some folders are missing from the ZIP

This can happen if certain logs do not exist on that machine.

For example:

• FSLogix logs may not exist on a local client machine.
• Teams logs may not exist if Teams is not installed or has not been used.
• Softdrive client session logs may not exist if Softdrive Launcher has not recently been used on the local machine.

This is expected behavior.

Additional Notes for Microsoft Teams Logs

If the issue is related to Microsoft Teams, have the user reproduce the issue first.

Then, while Teams is open, press:

Ctrl + Alt + Shift + 1

This generates Teams support logs in the Downloads folder.

After that, run the Softdrive Log Collector script so those files can be included when available.