FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: xSpeedbird on July 02, 2019, 10:42:00 pm
-
Hello,
I have recently been trying to update GSX to the latest version. However, when using FSDT Live Update, I am given the error "Object reference not set to an instance of an object". The header also states "Problem reading the FSDT registry key". I have uninstalled both Addon Manager and GSX itself and reinstalled and the same error persists. Does anyone know of a possible solution to this issue? Thanks in advance.
-
If you still see that error, it means you haven't the latest update, which gives you a more correct error message (which is not blocking), and it's usually related to having bogus registry keys for simulator you don't have anymore.
-
Is there a location where I can access this update? Or alternatively manually edit the registry?
-
Run the FSDT Live Update, of course.
-
When I run the Live Updater it just simply gives me that error and closes, and doesn't do anything else.
-
When I run the Live Updater it just simply gives me that error and closes, and doesn't do anything else.
That's because your Updater is not updated. Are you sure you started it from the Icon on the Desktop ?
-
As such?
&feature=youtu.be
-
Please check the date and time of the digital signature of the Addon Manager\Couatl_Updater2.exe file
-
Shows date modified as 7/2/2019 1:38 PM
-
Hi,
I am getting the exact same issue. My GSX was working fine until I ran the updater earlier. I have checked the registry for other simulator entries or 'bogus sims' and non exist in any registry location. I have uninstalled and completely removed all trace of any FSDT products and after downloaded and re installed the full installer from the website and I am still having this issue. This is the signature of the Updater2 exe https://gyazo.com/6636f09675aa7376269a87dcc860af18
Regards
Matthew
-
I'm sorry but, I cannot replicate your problem, and nobody else has reported that error after the update.
Please create a log of the update process, this way:
- Go the the Addon Manager folder with the Window File Explorer
- Open a new command prompt there, by typing "CMD" and then Enter on the blank address bar on top of the explorer windows.
- Type the following:
Couatl_Updater2.exe /LOG=log.txt
The updater process will run normally, and will create a log.txt file in the Addon Manager folder. ZIP it and attach it to a post, so I can have a look at it.
-
I followed the instructions as stated, I received the same pop up as before after running the updater via CMD, it was like I was running the updater normally. It didn't even create a log file for me to upload. https://gyazo.com/d8fd52f93e47cd73ed940fc3c54d3380 .
Matthew
-
I'm sorry, I gave you the wrong instructions, that log type is valid only for the 1st updater, the 2nd one must be programmed to be logged. I really need to check your system with remote assistance, send me PM if it's ok for you.
-
Okay, thank you, have sent you a PM
Matthew
-
What should I do in order to fix this issue?