Cause Analysis
PAD Design Limitations
Power Automate Desktop (PAD) uses a fixed file storage path, which users cannot customize.
It lacks an "automatic path correction" or "file relocation" mechanism; if a file path becomes invalid, it cannot be loaded.
Windows and OneDrive Integration
Windows 10/11 has a built-in "Known Folder Move" feature, which automatically redirects folders such as Documents and Desktop to OneDrive.
If PAD's files happen to be located in these folders, they will be synced to the cloud.
Consequences of Uninstalling OneDrive
When OneDrive is uninstalled or emptied, Windows does not automatically move these folders back to their original local paths.
PAD also lacks a file correction mechanism, resulting in files disappearing or failing to load.
Summary
This is not simply a PAD bug, nor is it a OneDrive bug.
The root of the problem lies in the Windows system design: it forcibly directs folders to OneDrive, but fails to automatically correct this after uninstallation.
Because PAD lacks path flexibility and a correction mechanism, it is inevitably affected, rendering process files unusable.
In other words, this is a result of both the Windows and OneDrive integration strategy and PAD design limitations.
👉 Simply put: the reason PAD process files are unusable is due to a design flaw caused by Windows directing file paths to OneDrive without automatic correction after uninstallation, coupled with PAD's lack of path flexibility.