How to Fix the “We Couldn't Set Your Default Save Location” Error in Windows 11/10 - Windows Basics


Tuesday, August 22, 2023

How to Fix the “We Couldn't Set Your Default Save Location” Error in Windows 11/10

Users have reported error 0x80070005 or 0x80070539 arising when they try to put new apps to save to different external hard drive locations using Settings. Those error codes have the same message saying: “We couldn’t set your default save location”. This means that the user cannot change the default save location for the application.

Does that bug also prevent you from changing where to save new apps to? If that's the case, here's how you can fix error code 0x80070005 or 0x80070539 on Windows 11/10.

1. Set your user account to administrator

If you are using a standard Windows account, change your user account type to an admin account. The standard user account will prevent you from applying any complex system changes. Changing the location where the app is saved is something you may need administrator privileges for.

2. Rename the WindowsApps folder

This error can arise because the WindowsApps folder where the application is saved is corrupted. Renaming the WindowsApps folder on the drive or partition where you want to save apps can solve such problems. To do so, rename that folder as follows:

1. If you're trying to put apps on an external hard drive, connect that hard drive to your PC.

2. Open the File Explorer folder navigator and click This PC.

3. Double-click the drive/partition you want to set as the default save location for the application.

4. Then, right click on the WindowsApps folder and select the Rename context menu option. You will find that folder in the root directory of the drive.

5. Rename the folder to WindowsApps.old and press Enter.

6. Then try changing the default save location for apps again through Settings.

If this still doesn't work, then move on to the next solution.

3. Delete or rename the WpSystem . folder

Many users confirm that renaming or deleting the WpSystem folder fixes error 0x80070005. WpSystem is a directory created to store application data. Try renaming that folder to WpSystem.old on a drive that you can't set as an application save location, as stated for the previous method. WpSystem will be in the same folder as the WindowsApps folder.

Also, delete the WpSystem folder. You can delete a file or folder in Explorer by right-clicking the file or folder and choosing Delete. If you can't find that folder or this potential solution doesn't work, try the next solution.

4. Set full system permissions for the System Volume folder

Setting full permissions for the System Volume folder is another confirmed fix for error 0x80070005. Follow these steps to set full permissions for the System Volume folder:

1. Go into File Explorer and click the three-dot menu See more > Options. In Windows 10, click Options on the View tab.

2. Select View on the Folder Options window.

3. Uncheck the option Hide protected operating system files (Recommended).

4. Select Show hidden files, folders and drives.

5. Click Apply to save the new Explorer settings.

6. Select the drive you need to set as the default application save location.

7. Right-click the System Volume Information folder and select Properties.

8. Click Security > Advanced to display the Advanced Security Settings window.

9. Click the Continue button.

10. Next, click Add to see the Permission Entry window.

11. Click the Select a principal option.

12. Enter SYSTEM inside the object name box.

13. Click the OK button.

14. Select the Full control permission setting.

15. Then select the OK options on the Permission Entry and Advanced Security Setting windows.

Close all remaining open windows. After that, restart your PC and try changing the default save location.

Set new default save location in Windows 11/10

Many users needed to fix error 0x80070005 and did so by applying the potential solutions in this guide. The WpSystem folder is often the source of the error and the second solution is the most widely validated method to fix this problem.

However, some users have also fixed the problem by applying the less cited fourth method.

No comments:

Post a Comment