Jump to content

Machine ID lock, after fresh new operating SSD installed, halp.....!


Recommended Posts

Posted

Hey team,

Back in August 2022, I had an SSD with my operating system (OSX-Mojave) running on it freeze up and die. #rip

I subsequently installed a new SSD, updating my operating system (OSX-Catalina).

When I went to log into XPlane-11, I started getting the activation issues.

As my machine ID name changed, I believe this is the issue.  As the machine ID previously recorded was different.

I logged a support ticket on the 1st and 12th of August 2022, still neither not being responded too.

I have removed Gizmo and attempted fresh installs of X-Aviation SAAB340. Nil result.

Attached are screenies and log.txt 

Any help here would be amazing!

457440620_ScreenShot2023-01-03at2_04_50pm.png.3b45ca1d6282f6cc1bbf7d0fdb2ed2a2.png

 

Screen Shot 2023-01-03 at 2.05.15 pm.png

Log.txt

  • 1 month later...
Posted
On 1/3/2023 at 3:49 PM, Ben Russell said:

Are you running a hackintosh build or genuine apple hardware? 

Hi Ben,

Sorry for the late reply, have been away overseas for an extended period.

As per my previous 2 other builds, I am running another Hackingtosh build.

Never had an issue from the earlier ones, and am stumped.

Are you aware of my issue? Is it a simple naming convention issue?

Posted

Hackintosh have a "special case" code path in the machine Id code... 

Please raise a ticket with X-A support so we can gather some diagnostic info based on your registration attempts and the machine Id it sent us. 

This is not something that is likely to be resolved without changes to the plugin code. 

A new plugin release is not far away though(days to weeks) so hopefully we can get this resolved fairly soon.

  • Like 1
Posted
17 hours ago, Ben Russell said:

Hackintosh have a "special case" code path in the machine Id code... 

Please raise a ticket with X-A support so we can gather some diagnostic info based on your registration attempts and the machine Id it sent us. 

This is not something that is likely to be resolved without changes to the plugin code. 

A new plugin release is not far away though(days to weeks) so hopefully we can get this resolved fairly soon.

Hi Ben,

Thank you for your prompt reply.

I raised Ticket/s (#M6BU0 and #QH4AK) back in August of 2022, with no reply.

Would you like me to close them off and re-raise a whole new one?

Let me know.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...