Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/tanmoy2504/snippingtoolfix

Guide & Script to fix the ‘Screenshot copied to clipboard, but couldn’t save’ error in Snipping Tool for Windows 10/11
https://github.com/tanmoy2504/snippingtoolfix

fix guide registry-scripts registry-tweaks snipping-tool windows-10 windows-11

Last synced: 6 days ago
JSON representation

Guide & Script to fix the ‘Screenshot copied to clipboard, but couldn’t save’ error in Snipping Tool for Windows 10/11

Awesome Lists containing this project

README 

        
# SnippingToolFix

Guide to fix the **‘Screenshot copied to clipboard, but couldn’t save’** error in Snipping Tool for Windows 10/11 



Original Credit goes to MiniTool for documenting the fix [Here](https://www.minitool.com/data-recovery/windows-not-saving-screenshots-to-screenshots-folder.html#:~:text=Step%201.%20Press%20Windows%20%2B%20R%20key%20combination)






> [!NOTE]

> I have created a registry file named **SnippingToolFix.reg** which can be downloaded and imported directly instead of manually tweaking registry. This will reset the directory location to default and incase the registry are missing, it will create the respective entries explained below. 

 **However users still need to create the folders in respective directories** or they can use the code inside command prompt to automate the same





> [!WARNING]

> This goes without saying that since we will be editing registry, it will be wise to make a ***registry backup or a full system backup*** incase of a mishap. _By proceeding forward, you are acknowledging the risks involved and that I shall not be held liable_ incase of damage caused to your system. 



> This event shouldn't occur unless user makes some mistake or change any setting which is not mentioned in this guide hence the strong recommendation for a backup



### The Problem: 



The error occurs when the “Screenshots” folder inside the “Pictures” folder is missing or if the user uninstalls OneDrive.

The Windows registry points to an invalid location, triggering the issue.





### The Solution:



Navigate to “HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer”





Create a DWORD (32 Bit) Value  named **Screenshotindex** vith value 1 (in Hexadecimal mode) 




Now navigate to “HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders.”




Correct these two registry entries: 




>{B7BEDE81-DF94-4682-A7D8-57A52620B86F}  ->  (points to the Screenshots folder location)



>{EDC0FE71-98D8-4F4A-B920-C8DC133CB165}  ->  (points to the snipping tool's screen record folder location)






Edit the data in the entries so that the folowing keys have the following values: 



{B7BEDE81-DF94-4682-A7D8-57A52620B86F}   ->  %USERPROFILE%\Pictures\Screenshots



{EDC0FE71-98D8-4F4A-B920-C8DC133CB165}   ->  %USERPROFILE%\Videos\Captures






>[!TIP]

>**It is best to use %USERPROFILE% for reliability instead of hardcoding the folder location unless the user wants to point to different location other than default.**






Create folders named “Screenshots” and “Captures” in their respective locations.



Alternatively you can just run the following command in command prompt to make the job easier 



```

mkdir %USERPROFILE%\Pictures\Screenshots && mkdir %USERPROFILE%\Videos\Captures

```





> [!WARNING]

>**The app expects the folder "Screenshots" and "Captures" to exist; Snipping tool app won’t create it automatically. Users must manually create the folder or use the command above, else the errors will persist.**






Close the Snipping Tool and restart explorer.exe from the taskbar or give it a full restart whichever is convinient






> [!IMPORTANT]

> If the registry entries **{B7BEDE81-DF94-4682-A7D8-57A52620B86F}** and **{EDC0FE71-98D8-4F4A-B920-C8DC133CB165}** don’t exist, right-click on “New > Expandable String Value” which will create a key with type **REG_EXPAND_SZ**. Now create the entries, ensuring the curly brackets are included or use the registry file to avoid the hassle 


- [x] {B7BEDE81-DF94-4682-A7D8-57A52620B86F} registry key name is valid

- [x] {EDC0FE71-98D8-4F4A-B920-C8DC133CB165} registry key name is valid

- [ ] B7BEDE81-DF94-4682-A7D8-57A52620B86F is invalid

- [ ] EDC0FE71-98D8-4F4A-B920-C8DC133CB165 is invalid