← Back to forum

Closed thread. This archived forum is read-only: replies are closed. Closed by archive.

Display names, replies, and the view count are editorial. They are not accounts, purchases, bans, customer testimonials, or a record of customer activity.

PC Support

Sea of Thieves tool setup problem, what should I check before changing Windows settings?

firstvoyage OP

Started Sep 24, 2026, Last reply Sep 24, 2026, 11 replies, 3,749 views, Closed thread. Closed by archive.

General PC troubleshooting question.

When a tool has a long requirements list and doesn't behave as expected, how do you work out which requirement is relevant without randomly changing a bunch of Windows settings?

I'm particularly cautious about anything involving Secure Boot or Core Isolation.

11 replies, Sea of Thieves tool setup problem, what should I che…

  1. Reply 1

    pccheck

    Start by writing down the exact error and checking the provider's documentation.

  2. Reply 2

    OP

    Would you contact support immediately?

  3. Reply 3

    pccheck

    If the documentation doesn't explain the error, yes. Better than experimenting with security settings.

  4. Reply 4

    specsheet

    The current ZADEYO page gives an address for support through its website ticket system and Discord. It asks customers to include their order ID for product support. (Product listing)

  5. Reply 5

    anchorplease

    Just don't share passwords or account recovery information in a support chat.

  6. Reply 6

    OP

    Obviously, but good reminder.

  7. Reply 7

    deckhand42

    I'd also separate game problems from product problems. If the game itself doesn't launch, start with official Sea of Thieves support.

  8. Reply 8

    OP

    Good point. The game runs normally here, so that narrows it down.

  9. Reply 9

    pccheck

    Next step should be asking the provider which documented requirement relates to the specific error. Don't disable security features based on a guess.

  10. Reply 10

    specsheet

    Agreed.

  11. Reply 11

    OP

    That's the sensible approach. Exact error, requirements, documentation, then support if needed.