WORK ORDER HD–01 / CONNECTION REQUIREMENTS
Know the gate. Take the safe next step.
Account mode, launcher source, edition, version, and the exact result each close a different connection gate. Enter only those five local facts. Handshake Desk returns an ordered checklist without credentials, downloads, account access, or a server lookup.
LOCAL EVALUATION //// FIVE OBSERVED FACTS //// ZERO CREDENTIALS
WORK ORDER HD–01 / LOCAL DECISION DESK
Build your safe connection order
Choose five facts you can observe. The desk sorts local, deterministic guidance; it does not contact a server, store an address, inspect an account, or declare that any target is safe.
Checklist before any retry
- 01
Stop if software came from an unknown attachment or asks for credentials outside a verifiable Microsoft sign-in page.
- 02
Confirm the account mode, Java or Bedrock edition, and the version stated by the server. Change one condition at a time.
- 03
Keep the exact kick message. Use the matching guide below instead of installing a promised “fix.”
Complete all five fields to produce an ordered local checklist.
Kicked with a known message?
- AUTH–01“Invalid session”
Refresh the session in a safe order.
- AUTH–02“Failed to verify username”
Separate client, service, and target clues.
- KEY–01“Secure profile required”
Understand the account-side requirement.
- PROTO–01“Outdated client / server”
Align the two protocol generations.