longbreak754

You may find the info on this WEBPAGE useful....

Hi Max, Yes, your version is the regular version - either the Standard version or Deluxe version. The box should tell you what version it. In the Steam version there would be a 'Steam Edition' sub logo directly under the Flight Simulator X logo located at top left. WRT to the -400 issue - it is worth noting that PMDG actually says that only a minority (about 1% in their estimations) can't get it running under Win10. As I stated in post #17, its most likely down to individual PC setups. Another possible reason that it is failing to install may be due to 'un-registered' or 'incorrectly registered' OS related dynamic link library files. These files, which have a .dll extension, are accessed by many programs and basically they contain instructions that programs can call upon to do certain things. See HERE for more info. I know that the info is related to a different error message but it is still relevant as it is another 'Access Denied' variation. It may help you get the -400 installed. One thing I will say is that you may need to use Admin rights to run the process. If so, substitute the given procedure to access the Run cmd box with this one: 1. Right Click on the Start Menu Icon. 2. Select the Command Prompt (admin) option from the list.

Hi Max, Plse clarify - What item shows 'steam edition'? - FSX (which based on what you posted earlier is the boxed version) or the -400. Where did you purchase/download the -400 and are you able to ID what version it is from the purchase/webshop info. Possible solutions (based on assumptions whilst we await the answer to the above question).... If your FSX is the boxed version and the -400 is the steam version: AFAIK items specifically stated as for FSE-SE (i.e. steam version) only MAY not work with the boxed version, whereas many of products designed for the boxed version can be installed into the steam version. Although the steam version is based on the boxed edition of FSX Gold (i.e. the Deluxe version of FSX with the Acceleration Addon included) they have may some updates that some Steam only products may take advantage off - see HERE for details of the updates made. SOLUTION: Option 1 - Contact the vendor and see if you can swap out -400 steam version for the -400 boxed FSX version. However, bear in mind that it may still not work as it doesn't for a minority of users as indicated in the linked page given by il88pp at post #13. The reason for this will most definitely be related to an individual's PC and its setup. Most likely, IME, this will be due to other missing core OS related libraries (of which C++ 2008 is one example) that FSX and thus addons, needs. Option 2 - Purchase/Install the Steam version of FSX and try install the -400 again. If your FSX is the Steam version and the -400 is the non steam version: Option 1 - Contact the vendor and see if you can swap out -400 boxed FSX version for the -400 steam version.

Hi Max, You will find the Visual C++ 2008 Redists packs at the following links: 32 bit - HERE 64 bit - HERE You will need to download the relevant file that is appropriate for your OS bit rate version. DO NOT run the install directly from the download option but SAVE the file to a temp location. Then run the file by RIGHT clicking on it and selecting Run As Admin. Once it has installed reboot the PC using the RESTART option. You can check to see if you have a version of Visual C++ 2008 already installed by looking in the Programs and Features listing but I still suggest downloading and installing as indicated above. This will ensure that you have no missing or corrupt files from a previous install - if you do already have an install of 2008 the redist pack install process will simply check what files are there and will only add and/or replace missing/corrupt/damaged/out of date files as appropriate

Try this... Check the properties of the downloaded PMDG file by right clicking on it. Look at the very bottom of the General tab and see if the file has been blocked - there may be a statement regarding blocking with a box to the right of the statement which is labelled Unblock. Click on the box to activate it and then click Apply followed by OK. Try running the install again using Admin rights.

A probable cause and a possible solution...…. It appears that they are updating the look of the website and attempts to go to use the old site are failing... Tried to access the site, via my saved browser link and via my password manager tool, and couldn't get on. I then used google to search for FSPILOTSHOP and selected the top entry that google displayed. This took me to a revamped site which, although having a 'Site Under Construction' entry at the very top, has functioning menus that take you to the chosen areas. Clicked on the Login button (located at top right) and got a login page which contains two options - login (which was auto-filled by my password manger) and New Account. Clicked on the login button and was redirected to a page that that displays the statement 'It looks like you're returning from the old site. Reset your password here.' - this page has a field for your email address and a Submit button. Filled in the box and hit the submit button and got a email back with a reset link. This link takes you to a password reset page. Reset the password and then log out of the site. Log back in and you then get a 'Verify Email' statement - there is a short statement under the main statement with a link in it to receive a verification link email. When it is received click on the provided link and you will get a Verification statement. I was then able to use the site and view my previous orders using the link provided under the profile name located at top right of the home page

…..AND FURTHER TO MY LAST POST.... Another option would be to disable UAC - this does has some security risks associated with it so google info on what these are and how to disable it.

The error code is usually associated with access permissions.... As your rig is new I suspect that it has Win 10 - the inbuilt security app (called User Account Control (UAC)) that ships with Win 10 seems to be more 'proactive' than the version used in earlier versions of Windows and seems to cause more problems. I also assume that you have installed FSX into the default location (C:\Program Files (x86)\………) - this again can cause issues for some users and again, whilst it affected earlier versions of Windows, it seems to be more of an issue in Win 10. This problem can also impact on other actions that you may want to do with regards to FSX - such as editing Aircraft.cfg files, etc. Two options available to you: A. Uninstall FSX and reinstall outside of the default location in its own root folder - i.e C:\FSX. B. When installing stuff run the installer using admin rights as follows: 1. When you insert the DVD cancel any autostart. 2. Use windows explorer to view the contents of the disk and find the install execution file - it will usually be named setup.exe or setup.msi but may have a different name. Whatever it is called it will have a .exe or .msi extension. 3. RIGHT click on the .exe file and select Run As Administrator from the resulting menu.

Hi Jacob, This looks like an issue caused by where the individual scenery items are sitting in the scenery priority listing - especially the ORBX libraries. Try moving the ORBX libraries down the list as low as possible but still keep them above the default FSX areas.

How are you trying to install the .NET...… Best practice, especially with Win 10, is to 1. Download and SAVE the .NET file to a temp location. DO NOT RUN it directly from the download link. 2. Right click on the saved file and select the Run As Administrator option. This will run the .exe with admin rights. 3. Once the install process has finished reboot the PC using the RESTART option - DO NOT USE the Shutdown followed by power on method.

Hi Col, Look at post #8 - CRJ_simpilot posted a link to 6 such tools...…….

If you have followed the various links that have been provided in this thread, and depending on what options you have selected you should only receive updates to the OS itself and, if set, other MS products you may have installed (i.e. Office, Internet Explorer (if you still use it) etc). You cannot stop all updates using the options contained within the various windows settings - security and compatibility updates will still occur. If you really want to stop Win 10 updates completely, you will need to use 3rd party apps to do so, as suggested in some of the other posts. It could be that Canon did not release any 'new' drivers via MS until now. Also, it seems to have become the norm to use a standardised 'driver' package that combines many common files/drivers for all versions of a product produced, that release of 'universal' driver updates

Hi Charlie, I only suggested the MSXML 4 SP2 file to resolve the language .dll issue that was reported in post #12 as the wording of the error message implied that there was a problem with his MSXML 4 component install..... I also thought that I had made very clear in subsequent posts (#20 and #22) that it was a totally different SP2 to the FSX SP2.....

As Charlie has stated it appears that you don't have the FSX SP2..... To clear ANY confusion - The FSX SP2 is a totally different file to the MSXML 4 SP2 I suggested that you install in my earlier post. The FSX SPs (1 and 2) are FSX specific files whilst the MSXML 4 SP2 file is an OS based system file that FSX and other programs make use of when required....

Like Larry I have not seen/heard of airspace labelled as "Dangerous" but I have seen/heard of areas labelled as "Danger Area" - these are often ranges and/or military ground training areas where live firing takes place.

Yes. The icon will still be there and will still function because it is aligned to a file created during the initial install - usually a file that has a .exe (short for executable) or, sometimes, a .bat (short for batch) extension. As Vic has stated in post #15 - follow the instructions and only delete those files/folders specified and you will have no issues.....

In real life many of these areas will be there for a specific reason and will have specific restrictions assigned to the area in question. This often includes heights, timings etc. Where there are such restrictions, such as height for example, you will be able to overfly the area in question unimpeded as long as you are above the minimum height For example these areas are often around sensitive military airfields, military testing areas and weapon ranges, government buildings, government/state owned residences, power stations, , jails etc. Some, like military testing areas and ranges, will be only active for short periods and will normally be notified by NOTAM.

What is meant by this statement is that the files can be deleted because when you run the sim again they will be automatically recreated. A number of files in FS products act this way. They are often files that are not created during the initial installation process of the main program. They are only created when you first run the sim. Examples of such files vary according to the sim being used but common ones are the main sim .cfg file (i.e FSX.cfg, P3D,cfg etc), Scenery.cfg, Pilots Logbook, Controller assignment etc. If you are worried about deleting them you could make copies of them and store them somewhere outside of the main sim folder.....

Hi Col, As you will know I have often made comments about how I keep most of my scenery outside of the default FSX Addon Scenery location - indeed, I store it outside of FSX... There are two options you can use to get around this and use the modified AFCAD file.... Option 1 - A. Create a new folder inside of the default FSX Addon Scenery folder - e.g. Addon Scenery\My Airport Files. B. Create the two required subfolders (Scenery and Texture) within this new folder - eg Addon Scenery\My Airport Files\Scenery. C. Activate this folder location in FSX as normal. Method 2 - As method 1 above but create the folder either as a new folder within the FSX root directory - e.g FSX\My Airport Files\….. - or outside of the FSX - e.g C:\My Airport Files\….. The selected location outside of FSX can even be on a different harddrive from FSX if required. Both methods will then allow you to keep the new folder above both the default Addon Scenery folder AND the ORBX folder.

There are numerous ways to reduce the amount of updates you get via the WU process and to minimise the amount of data collected by MS - a simple internet search is all that is required. @ REDDAIR Although you have resolved the issue by getting older drivers, it is possible that the next time windows updates that it will redownload and install the incompatible drivers. You can turn off all non MS developed/related driver updates using the info found in these two links - LINK 1 and LINK 2 WRT the specific cartridge problem that REDDAIR has reported - the problem is a common theme and IS NOT directly related to a MS update file itself but via a driver update provided to MS by the OEM software team. It is now common for all printer manufacturers to make it harder for users to use 'cheap' refills. Most new printers are already 'hardwired' as such and many have applied this to older printers via a firmware update, either issued directly via their own update process (as part of the installed driver software - check to see what update policy is in place via the specific printer software installed) or via an update issued to a third party source (such as MS).

@ Trent, Further to my last post, something else that you can try.... Sometimes, especially with payware and more detailed freeware, the scenery is made up of separate .bgl files that contain the various elements of the scenery. Look in the scenery subfolder where you have installed the scenery and check to see if the author has provided the tree objects as a separate .bgl file. Look for files with names like trees.bgl or vegetation.bgl. If so, simply rename the file by adding .BAK to the end of it (i.e. trees.bgl.BAK) or simply remove the file. Of course, this will mean that no trees will be displayed.

I use loads of FS2004 stuff in FSX and for the most part have had very few issues. IME the main problem encountered is how FS2004 trees are displayed and how some file types normally used in FS2004 can cause issues. WRT the tree issue - As il88pp has pointed out, usually only the author of the scenery can legally edit the scenery, especially so in this case as it is payware. However, some payware authors may allow, via the EULA, editing of the scenery for personal use only. So check the EULA/Copyright info to see if that is the case here. Usually, freeware is more liberal and you can often edit it and, in some cases, post it for use by others. WRT the comments made by Charlie regrading CTD issues - the main culprit for this is the use of files that contain VTPL VTPP, VTPX and LWM2 descriptions within the filename. These are landclass/ground poly scenery files (i,e they have a .bgl extension) that that do not play well with FSX and deleting them often clears the issue with little noticeable difference to the scenery

And if you look further down the page below the V11 entry you will see entries for V10 and V9 as well, if you are after an earlier version...….

If you want X-plane on CD get it at the X-Plane store....you can get the latest version and earlier versions if required..... Here is the LINK