SpoofHWID Support

The primary support channel is the private ticket inbox inside your SpoofHWID account. Try the matching self-service path first; if it does not resolve the issue, include its result in your ticket.

Start with the correct page

• Status — confirm that the game or environment is in current product scope. A blog guide does not establish compatibility.
• Sign in — use your UDPCloud application username and password, a verified-email code, or the password-recovery flow.
• Create an account — create a verified recovery account before attaching reseller-issued access. A license is not required to register.
• Account — manage subscriptions, create application credentials when required, redeem a reseller key, download an active build, reset a device binding when eligible, and open a ticket.

Password and sign-in recovery

Your application username and password can also be used to sign in to the website after the account is linked. If you know those credentials, begin at Sign in.

If the account already has a verified recovery email, choose the password-reset option on the sign-in page. The site sends a one-time code to that linked address and then lets you choose a new application password. Email-code sign-in is also available for an existing verified account.

Password-reset messages are intentionally generic. Check filtered mail, use the linked recovery email, and retry with only the newest code. Never send a password or one-time code to support.

If you no longer control the linked email, open a ticket from an account you legitimately access. Creating another account does not move an existing license.

Connect an older UDPCloud application account

An older application account may have a username and password but no recovery email. Enter those application credentials on Sign in. After the credentials are accepted, the site asks for a recovery email and sends a verification code. Completing that email check links the existing application identity to the website.

Use an email you control for future recovery. The flow verifies both the existing application login and the new inbox. If either identity is already linked elsewhere, open a ticket with the exact message.

Redeem a reseller-issued license

If an authorized reseller supplied an unused license key:

1. Create an account or sign in to the recovery account you want to keep.
2. Open Account and select the Subscriptions tab.
3. Choose Redeem key and paste the key exactly as provided.
4. If no application login exists yet, choose the requested application username and password during redemption.
5. Confirm that the subscription appears on the same Account page before downloading.

A redeemed key becomes attached to that account. Avoid temporary or shared email addresses. Reconnect an older UDPCloud identity first if Account requires it.

For an on-site checkout, access is normally associated with the verified checkout email rather than entered as a reseller key. Sign in with that email and complete application-login setup from Account if prompted.

Open and follow a private ticket

After signing in, open Account, select Support, enter a specific subject, and describe one problem per ticket. Replies appear in the same inbox. You can leave the page and return to the Support tab later to read or continue the conversation.

Add new evidence to the existing thread instead of splitting one issue across duplicate tickets.

What to include

A useful initial report contains:

• a short issue category: sign-in, linking, redemption, download, device reset, or application launch
• the complete error message, copied exactly
• the page or application action that produced it
• the approximate date and time, including time zone
• Windows edition, version, and build for client issues
• application version, if the client opens far enough to show it
• whether access was bought on-site or issued by a reseller
• whether the affected title appears on Status
• the last time the same action worked and what changed afterward
• the troubleshooting steps already attempted

Screenshots should show the complete error. Redact unrelated account, device, order, and desktop details.

What not to send

Never include passwords, verification or recovery codes, session cookies, full card numbers, or remote-access credentials. Identify a license by its last four characters and purchase source unless private support requests more.

The established Discord community is secondary and suited to general announcements or discussion. Keep ownership, payment, license, and recovery matters in the private Account ticket.

Keep the request scoped

Support can investigate website accounts, application access, and supported product behavior. Publisher actions, community-server decisions, firmware settings, and unsupported titles belong with their respective owners. Preserve the exact error and keep account matters in the private inbox.