Windows 10: Bug when trying to access C:\Users\username\Desktop when already in...

When I open Paint and then save the image on C:\Users\harry\Desktop and then when i open paint again and click D:\ drive shortcut on the left panel of the "open image" window, and then paste the link C:\Users\harry\Desktop in address bar, it redirects me to C:\Users\harry\OneDrive\Desktop. Where ofcourse the image is not there because I stored it on C:\Users\harry\Desktop. This also happens when I click the Desktop shortcut instead of D:\. So there is no way for me to access exactly C:\Users\harry\Desktop directory. Unless I manually click through the folders from C:\ to Users to harry to Desk

:)

 

How to pin c-users-username to quick access not the desktop library of username?

EDIT: Pinning c-users-username-(folder) functions normally it is specifically c-users-username that is the problem

The problem occurred before the customization (which is simply use document template). It also fails to work on two other windows 10 laptops (all three devices are different manufactures and motherboards and parts). So it most certainly is not because I
changed the template. It also has occured for nearly a year now across every update, I even attempted on a clean install(using the media creation tool) without updating or installing anything and it also failed.

Just to make sure we are following the same steps.

I navigate to C:\users\ right click and pin to quick access

I click the link it creates

opens username(that library in desktop) and not C:\users\username

 

c:\users\username\desktop is not accessible

Thank you - it was bugging me too that it's c:\c:\ and not c:\users. I tried your suggestion and thought it worked when it found a few corrupt files but once I rebooted I got the same messsage

 

c:\users\username\desktop is not accessible

This is bugging me so I'll point out that the error message says "C:\C:\Users... is not accessible" where the path should be "C:\Users...", one C: only. I don't know why the system would be calling that wrong path. Maybe someone knows.

Try sfc /scannow?