F5F Stay Refreshed Software Operating Systems Deploying software to drive E:

Deploying software to drive E:

Deploying software to drive E:

B
BayernTobi
Junior Member
23
12-19-2016, 02:26 PM
#1
I've been using Windows 10 for about 20 years and I'm quite tech-savvy. My system has Win10 installed on its own M.2 drive, and I've also got X-Plane 11 running on the same M.2. There are instances when I run an installer.exe (downloaded to CSmile to add an XP11 extension on E: and I encounter this warning message. What's going on? Since XP11 is fully portable, I moved its entire 84GB folder to C: and was able to launch the installer. Why does Windows 10 behave this way?
B
BayernTobi
12-19-2016, 02:26 PM #1

I've been using Windows 10 for about 20 years and I'm quite tech-savvy. My system has Win10 installed on its own M.2 drive, and I've also got X-Plane 11 running on the same M.2. There are instances when I run an installer.exe (downloaded to CSmile to add an XP11 extension on E: and I encounter this warning message. What's going on? Since XP11 is fully portable, I moved its entire 84GB folder to C: and was able to launch the installer. Why does Windows 10 behave this way?

C
Cracotte69
Junior Member
16
12-24-2016, 08:25 PM
#2
It seems the add-on requires access to files on the x-plane installation. When you attempt to run it from another drive, it can't locate them. This might be a guess. Try executing it from the x-plane directory instead.
C
Cracotte69
12-24-2016, 08:25 PM #2

It seems the add-on requires access to files on the x-plane installation. When you attempt to run it from another drive, it can't locate them. This might be a guess. Try executing it from the x-plane directory instead.

S
SinhasGamerPT
Member
116
12-24-2016, 10:00 PM
#3
XP is entirely in E: and the XP installer worked regardless of whether it was on Windows C or in the XP E drive. After copying the entire XP folder to the C drive, everything installed smoothly.
S
SinhasGamerPT
12-24-2016, 10:00 PM #3

XP is entirely in E: and the XP installer worked regardless of whether it was on Windows C or in the XP E drive. After copying the entire XP folder to the C drive, everything installed smoothly.