#WINDOWS 10 MAPPED DRIVES NOT SHOWING INSTALL#
#WINDOWS 10 MAPPED DRIVES NOT SHOWING WINDOWS#

Most likely they have set admin rights to the software to be able to install packages into the C-drive library. If this is the case for you, you need to contact your own IT department to make them adjust these settings.

These packaged software can be installed from a university link without admin rights required and have various settings pre-registered. Most universities have a separate environment in which they offer packaged software to employees that can be installed, for example from something like a university 'software center'. If you have not downloaded and installed R and Rstudio yourself from the associated web pages (because you for example have not received admin or installation privileges from your university), you're most likely getting your R and Rstudio software packaged from the university. Some users in this rstudio github issue report it from a university setting.

#WINDOWS 10 MAPPED DRIVES NOT SHOWING WINDOWS#

This happens with most windows software that have an elevated start (the search indicates a cmd prompt as this was the easiest search to get to the link, but applies to R and Rstudio). A quick search on the web 'why cmd prompt not show network drives in admin mode' yields many links amongst which: As mentioned by running Rgui or Rstudio in admin mode runs a different set of environment variables / runs in a different context. This is not a bug in Windows, this is intended behaviour in Windows. Not sure if this still helps (but the issue is still open). You can use net use to give the admin account access to the network drive. Running net use in windows cmd with/without administrator level shows that windows cannot/can access the mapped network drives. When I run either as a regular user they both can access the network drive. I have checked and when I run R or RStudio as an Administrator they cannot see the network drive. When I ran R gui, initially I did not run it as an administrator and it could access the network drive fine. However, the actual problem was that I was running RStudio by default with the admin account (and the admin account doesn't have access to the network drive) but when I open a project directly RStudio launches only with regular user credentials and not as an admin. This led me to believe that opening a project that existed on the network drive was somehow allowing RStudio to see the network drive. I had set RStudio to always open as an administrator when I opened it from the task bar, but NOT when I opened a project directly. The problem I was seeing was coming from windows user environmental variables per. TLDR I don't think there is any difference between R and RStudio.

Windows 10 mapped drives not showing