Four days isn't unusual for that channel — Friday-to-Tuesday crosses a weekend, and these requests are usually handled in batches by whoever runs the tool, not by a support desk. So I wouldn't write it off yet.
A few things worth checking while you wait, because they're the usual reasons a request quietly stalls:
- Make sure the txt went out unedited. If you opened it, retyped it, or pasted it into the body of the mail instead of attaching the file itself, the HW string can pick up a stray character or a line break and the request gets binned as unreadable. Re-send the original file attached, not inline.
- Same subject line, same address as printed in the file. I don't have visibility into that mailbox, so I can't confirm anything arrived — only that the file is the intended channel.
- Check the HW ID hasn't changed. Run the tool again now and compare to the string in the txt you sent. If the tool is showing a different value than Friday's file, your old request is dead on arrival and needs re-submitting against the current one — NIC swap, dock change or a Windows update can move that fingerprint.
- Spam folder. The reply comes back from a free mail provider, which a lot of mail hosts happily filter.
One more: stop re-posting the activation request in the thread — from what I can see it doesn't reach the generator, and you're only exposing your own identifiers. If the file contains the full HW string, that's worth keeping to the private channel.
On the "MGU7carauto" naming — is that the archive and executable name you're running, or the string the tool prints in its title bar? And when you re-open the tool today, does the HW ID field match what's in the txt character for character? That tells us whether it's a waiting problem or a fingerprint problem.
