Encountering an annoying 2211 error when trying to install Microsoft FSX. While this is only a game I really would appreciate a solution in case I encounter this in a more urgent situation.
What is this and what causes it ? Any ideas anyone ? [:@]
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Error 2211 is detailed here.

I suspect the installer is trying to write a new table to a location where the account you're using while installing has no write permissions. ProcMon will show you what's going on. Remember to set a decent filter for PM, though: it reports EVERYTHING!
Answered 11/12/2010 by: VBScab
Red Belt

Please log in to comment
[;)] Almost embarassed to post this solution, however my view is that requesting help on a forum and not posting a solution if found is like not buying the round at the pub !!!
Got this far through a trawl of search info . . .


. . . and the 2211 error seems to have changed to 1607. Not absolutely sure if any procedures followed were the root cause of problem and what helped, but certainly the registry was littered with FSX keys (from so many attempts to install?) so hopefully improved the registry.

Still no joy until the embarrasingly simple realisation of the problem.
Remembered VBScab comment on permissions that I ignored as running XP on Administrator. No permission needed I thought. Then realised a possibility that I was attempting install using a virtual drive taking data from a network disk. The 'system install folder' (mentioned in links above) was not shared (and not recommended to have System folder shared) for obvious reasons). Appears transfer from network disk not allowed, or (more likely) the virtual drive, essentially being a program, does not have permission to write there, so Setup could not proceed. Burnt ISO onto DVD in old fashioned way, re-installed DVD drive (as took out to replace with 2 Solid State Drives OS and data) and away the install went.
Simple in the end, but should have thought of that sooner !!
As a side point this was a RE-Install (should have said in original post) as switching to Solid State Drives for speed increase for heavily disk reliant software (instead of load all and run). Highly recommended, the speed increase is worth it. [:)]
Answered 11/12/2010 by: Ballistic Mouse
Yellow Belt

Please log in to comment