MFA Reset Guide for ESET and Managed Accounts
Published November 17, 2026
By the Authenticator App Team
An MFA reset replaces or clears an enrolled verification method so the account holder can register a working replacement. If you use ESET HOME, try an unused recovery code when the app is unavailable. ESET directs users without a working device or recovery code to its Technical Support. For a native ESET PROTECT Hub user, an eligible superuser or administrator with write access can reset two-factor authentication for that user and trigger setup at their next sign-in.
If you use a work identity through Microsoft Entra ID, OneWalmart, or another managed service, start with the organization that controls the factor. Keep any working session and recovery option available until the new method passes a normal sign-in.
Decide Whether You Need an MFA Reset
| Situation | Try first | Who controls the next step |
|---|---|---|
| Code from a working phone is rejected | Check account, method and time | Account holder or authorized provider |
| New phone can restore a valid entry | Restore through the approved app and test | App publisher and account holder |
| Factor is lost or exposed | Use alternate access and request replacement | Service provider or authorized administrator |
| Work account uses a federated sign-in | Identify the organization that issued the challenge | Identity administrator for that account |
Distinguish a Reset From a Temporary Failure
A fresh code or the correct app entry can resolve a timing or account mismatch. An MFA reset changes the provider’s registration. Check the error and test any known working device before requesting it. If the active enrollment was exposed, replace it even if it still works. The goal in that case is to stop other copies from producing accepted proof, while keeping authorized access.
Identify the Provider That Issued the Challenge
Read the account address, login domain, and method name. An ESET HOME consumer account, a native ESET PROTECT Hub account, and a Microsoft Entra user accessing the Hub can have different administrators. A consumer password reset also does not necessarily change the enrolled factor. If you are unsure which party owns the MFA reset, open the product’s official sign-in and check where it directs you for account or security information.
Keep a Working Session and Backup
If you can still open the account from a trusted device, leave it signed in while you verify recovery. A trusted session may not be enough to modify security because the service can request additional proof. Check whether you have the old device, an unused code, or a registered alternate. Avoid deleting a working entry as a way to diagnose an unconfirmed problem.
For a simple example, a user who restores the authenticator to a new phone can still sign in with the old phone. Have them compare the actual account and test the restored entry first. If that succeeds, an MFA reset may be unnecessary. If the old device was stolen, review the service’s revocation and session controls even if a backup works.
Amazon Authenticator Setup and Two-Step Verification Recovery
Reset Two-Factor Authentication for ESET HOME

Use the Ordinary Code or an Unused Recovery Code
ESET HOME documents a six-digit app code for routine two-factor authentication and an eight-digit recovery code for backup sign-in. Use the method selected in the ESET HOME login. If you saved recovery codes at setup, find the current list in the protected place you chose and use an unused code. Do not send a code to another person or paste it into a general code generator. If neither the device nor a recovery code is available, ESET directs users to official Technical Support.
Review the Available Settings After Sign-In
ESET HOME’s online help describes opening the account’s Security settings and editing Two-Factor Authentication. The provider documents a password and app code check to edit the settings, so a recovery sign-in does not establish that every change can be made immediately. Follow the current prompt. Review the options for recovery codes and remembered devices. If you cannot complete the requested proof for the change, use ESET’s official support route instead of removing a device at random.
Re-Enroll Through the Official Account
If you still have the working app and the service offers a supported way to replace it, follow the ESET HOME setup for the new device. ESET’s mobile guide describes adding the account to a compatible authenticator, confirming its six-digit value, and saving recovery codes. Begamob’s is an option to review when the service and organization allow a compatible standard code. Test the new enrollment after the MFA reset and save recovery material outside the phone.
Treat a Remembered Device as a Test Constraint
ESET HOME documents that a device can be remembered for a period, and it provides a way to clear remembered logins. When you test the new factor, use a supported separate session so the original remembered session does not hide a failed enrollment. If a device was lost, review the official controls for remembered access. Keep a working verification route while testing any security change.
For ESET HOME, check which proof is needed to sign in and which proof is needed to edit settings. A recovery code may get you into the account while a separate change still requires stronger verification. Record the exact prompt before contacting ESET Technical Support. Do not include your eight-digit recovery value in the message.
Download Authenticator App
Secure your accounts with fast, reliable two-factor authentication. Download now and protect your login in seconds.
Follow the Authorized Path for an ESET Work Account

Confirm That the User Is Native to ESET PROTECT Hub
ESET documents that its Hub two-factor controls apply to native Hub users. When a user signs in through Microsoft Entra ID, that organization’s Entra environment controls the applicable MFA policy. Confirm the user’s sign-in type before starting an MFA reset. An ESET Hub administrator should avoid resetting a different native user because their display name resembles the federated identity.
Use the Per-User Reset in the Hub
For an eligible native account, the ESET PROTECT Hub guide instructs a superuser or a user with appropriate write access to select the person in Users, open their security settings, and use the reset control. The administrator verifies their own credentials and completes any additional confirmation. The reset applies to the selected user and prompts fresh setup at the next sign-in. ESET does not describe it as a company-wide reset. Check the role, account, and authorization before confirming.
Handle an Administrator Lockout Through the Supported Route
ESET documents conditions for a superuser or user with write access to receive an MFA reset from an authorized colleague. It also describes a backup-code route for eligible users to regain access and change the factor under the documented policy. If the company enforces two-factor authentication, consult the applicable constraints before assuming you can temporarily disable it. Use ESET Support when the documented recovery methods are unavailable.
Keep the New Enrollment With the Actual User
After the reset, have the account holder complete enrollment in their own session. The administrator can verify the outcome without collecting the QR, secret, or current code. Record which account was reset and which approved method now works. Where ESET supports generating new backup codes, verify that the holder saves the current list before the next device change.
During an ESET PROTECT Hub MFA reset, have the administrator open the actual user record and compare its email, role, and sign-in type with the request. Have the user start a fresh session after the reset. If the session still presents the previous prompt, check the identity and reset state before repeating the action.
Run a Controlled Reset Instead of Removing Every Method
| Checkpoint | What to confirm | What to keep private |
|---|---|---|
| Before approval | Correct identity, reason and authority | Passwords and recovery values |
| Before the change | Existing access or independent backup | Setup secrets and recovery files |
| After the change | New enrollment verified on the account | Current codes and QR images |
| At closure | Old method retired and access reviewed | Credentials in support tickets |
Verify the Request Through a Known Channel
If a reset request arrives by chat or email, use the provider or employer’s official identity verification workflow. Do not rely on a message from an unverified number. For a work MFA reset, record the account and authorized request without recording live credentials. Confirm the correct system, particularly when the same employee uses several single sign-on tenants or employee portals.
Decide What to Revoke and What to Keep
A lost phone, a replaced phone, and an exposed setup secret are different cases. If the old phone is still in the user’s possession, an approved transfer or re-enrollment can be tested before retirement. If it is missing or compromised, use the provider to revoke the affected registration and check active sessions. Keep an authorized independent method available during the change when possible.
Verify the Impact on Sessions
An MFA reset can affect future challenges without automatically ending existing sessions. If the account was compromised, follow the provider’s process for reviewing and revoking current access. Check contacts and new methods for unauthorized changes. Keep the incident record limited to the information needed to verify the repair.
Suppose a staff member works on a managed terminal and loses the personal phone used for a remote employee portal. The two sign-ins can have different enrollment rules. Identify which service issued the challenge, verify the employee through the approved support process, and request an MFA reset only for the affected registration.
Check the Employer Route for Walmart and Other Work Accounts

Identify the Employee Service and Network Requirements
For a Walmart 2 step verification reset, start with OneWalmart or the employer’s approved associate support route. OneWalmart support materials distinguish personal-device access from some workstation or VPN factors, and the help route may vary by role or country. Verify which employee service needs access. A method that works on a managed workstation may be registered separately from the factor used when you sign in off-network.
Ask the Authorized Help Desk About the Old Registration
If your phone number or device changed, check the available approved path to update or remove the old enrollment. OneWalmart support materials indicate some changes require help desk involvement. Ask the appropriate associate support line which method applies to your account and location. An MFA reset for a customer shopping account would not update an employee credential, so confirm which identity you are recovering.
Do Not Assume Every Employer Uses the Same MFA App
A managed employer may require Symantec VIP, Microsoft Authenticator, a hardware key, or another method depending on policy. Use the method presented by the actual account and approved by the help desk. If a support page asks you to sign in on the corporate network, use the authorized route. Avoid enrolling a personal code app merely because it can scan a QR from another provider.
If you receive conflicting instructions about a work MFA reset, ask the help desk to identify the official portal for your account type. Keep the known device available. Document whether the issue occurs on the workplace network or off it. The user should only add the new method through the account and app approved for that path.
Re-Enroll and Verify the New Factor

Open a Fresh Enrollment After the Reset
Return to the official account after the provider reports the MFA reset complete. Select the approved method and complete the confirmation. If the account issues a new QR, use the entry that came from the current screen. Keep the setup QR and any manual key private. If the workflow uses a managed approval, verify the current device registration rather than relying on a restored app label.
Test the Ordinary Sign-In and the Recovery Path
Use a separate trusted browser or client while the existing session stays available. Confirm that the new method completes the expected sign-in. For a work account, test in the environment the employee normally uses. Check that a recovery route still works after the reset. If the old phone was lost, review whether additional sessions or tokens need revocation under the provider’s policy.
Close the Support Record With the Outcome
Record the factor type, whether the user completed enrollment, and the date of the verified login. Leave setup keys, recovery codes, and live values out. If you cannot finish the test, record which step is still pending so the next support person can continue without issuing a second reset. Ask the user to verify access to the relevant product, such as the ESET console, after they regain the login.
Test after the MFA reset from a browser that asks for the new factor. An open session that skipped verification is still useful for recovery, but it does not prove that the new registration works. Check that the user reached the correct identity and product. Verify that any documented backup route still applies.
Troubleshoot a Failed Reset Without Repeating It
Verify Which Identity Was Reset
A user may return to a cached sign-in for a different account. Check the exact username, tenant, and browser profile. If they still see the old MFA prompt, confirm whether the change was applied to that identity and whether the provider is waiting for a fresh sign-in. An MFA reset in one provider will not change the factor registered with another.
Distinguish Missing Setup From Rejected Confirmation
If the account does not offer setup, check whether policy requires an administrator or another verification step. If setup appeared and the current code was rejected, compare the app entry, account, and device time. Test one correction at a time. Keep any fallback that still works, and ask authorized support to check the status before repeating the reset.
Check for Exposed Data During Support
Keep live codes and setup screenshots out of tickets and screen shares. If someone received a copy of the current setup key, tell the authorized support team what material was exposed without repeating it. The provider can replace that factor and review active access. If the issue was only a display error, avoid unrelated changes to the account.
If an MFA reset was ordered after a suspicious sign-in, check whether the old enrollment and sessions were revoked separately. Confirm the final policy, access, and recovery state with the authorized administrator. Close the request only after the user completes the intended login or the unresolved step has been recorded for follow-up.
Questions About an MFA Reset

Will a Password Reset Replace the Authenticator?
A password reset changes the password. The enrolled factor usually has its own controls. Check the provider’s policy and verify both methods after any suspected exposure.
Can I Reset MFA From a Remembered Device?
A remembered session may help you reach account settings. The provider can require fresh proof to change a factor. Keep the session, check the authorized recovery choices, and ask support if you cannot complete the change.
Can I Use My ESET HOME Recovery Code for ESET PROTECT Hub?
Use a recovery or backup code only for the account and product that issued it. ESET HOME and ESET PROTECT Hub have separate controls. Identify the sign-in service before entering a value.
What If the Reset Says Setup Is Still Pending?
Open a fresh sign-in for the correct account and follow the enrollment screen if shown. Ask the administrator to confirm the state if you cannot see it. Record the exact message and method without sending credentials.
Is Removing the App Entry Enough After Losing a Phone?
Removing one copy does not necessarily revoke an active service enrollment. Replace or revoke it through the provider and review any sessions associated with the lost device. Verify the replacement before closing the case.
Final Thoughts
Start an MFA reset with the provider that controls the affected identity. For ESET HOME, try the documented recovery code and contact ESET Technical Support if you have neither that code nor the device. For a managed ESET PROTECT Hub, Entra, or OneWalmart sign-in, follow the authorized organization route.
Keep any working proof while the change is in progress. After the reset, enroll the approved method and verify a normal sign-in. Review old registrations and store an independent backup before you need it again.
Download Authenticator App
Secure your accounts with fast, reliable two-factor authentication. Download now and protect your login in seconds.