


If this turns out to be a simple case of: Access Denied (because path exists) and not Access Denied (because Micro$oft thinks you're a ham-fisted ape that shouldn't be allowed near a calculator, much less a PC), I am going to be very butt-hurt. I just spent hours after the Non-Volatile going through to check to see what, if anything, may have been helped by it.
#Default folder x not starting install
a (Non-Volatile) Repair Install and in the worst case, followed by a (Volatile) Clean Install of Lindows. So I then tried Microsoft's favorite go-to Fix-All. Text editor (Notepad, Sublime, Atom, etc.) Download Arduino IDE (Option 1) Download Visual Studio Code (Option 2) Configuration.h file. Preparing our PC (necessary files) Downloading the Marlin Firmware. Thought it was permissions = Access Denied, and went through all the iterations of setting owner/access to all the folders I knew were involved in the process of installing/updating/maintenance of Store/UWP Apps. Marlin Builder: Configure Marlin via web. A new Windows Update got installed and even more started to give the error as the Apps started their obligatory 'after-update-updating'. Then other apps that I use infrequently started reporting the error. For example, if you set options for Icon view, then click Use as Defaults, all folders that use.

At first it manifested with my printer app days after installing the XBox Beta App. The Use as Defaults button does not appear for Columns view. I have been recently struggling with this error. Once you have done that you shouldnt have any issues. If that is the case, what you need to do is either rename the old directory that is already there before you start moving things, or go into the directory and rename the folders that are causing the issue. You will get that error is there is already a directory structure there with the same name, so if you have re-installed windows and gone back in to redirect where its all to be saved again. Ok, I know this thread is an old one, and the OP and others who posted having this issue have likely fixed it, but it will help others in the future.
