Why Does Hurco WinMax Ask for an Administrator Password?

Hurco WinMax disappears and the panel stops at a Windows sign-in screen showing Administrator after a network configuration change and restart. Start here: decide whether Windows is blocking the control at sign-in or WinMax is running and only the network share is blocked. Those are different faults.

Identify the screen before changing anything

Read the panel exactly as it stands. Do not start by rebuilding the network connection.

A VMX64i entered the Administrator sign-in screen immediately after Windows restarted to apply networking settings. That sequence points first to session access, not to damaged WinMax software.

Check the sign-in state first

Take one reading: note the displayed account name. If it is not Administrator, do not apply credentials intended for that account.

1. Photograph the complete screen before entering anything.
2. Confirm that Caps Lock is off and that the keyboard layout produces the expected characters.
3. Leave the password field empty and submit it once. An installation that never had an administrator password may still accept a blank value.
4. If blank fails, record the message without repeatedly retrying credentials.

A blank field on the screen does not prove that the password is blank. Windows masks stored credentials and presents an empty entry box at each sign-in.

If Windows reports an incorrect password, continue to the credential check. If it reports an account restriction, lockout, or another distinct condition, preserve that wording and move to recovery planning. Repeated guesses waste time and can complicate access.

Test only the documented credential candidates

Two exact values resolved or were proposed for this symptom on Hurco installations: hurco and 86264. The latter was described as Hurco's ZIP code in reverse. Treat both as installation-specific candidates, not universal factory credentials.

1. Try hurco once with the displayed Administrator account.
2. If it fails, verify the keyboard output and try 86264 once.
3. If either value opens Windows, do not immediately alter accounts, policies, or passwords. First confirm that WinMax launches and that the control reaches its normal operating screen.
4. If both fail, stop guessing. The password may have been changed during commissioning or service.

The successful hurco case followed a networking tutorial and restart. That makes it the stronger resolving branch for the same visible condition. The evidence does not identify controller software versions, Windows versions, or a model-wide credential policy, so these values must not be treated as guaranteed defaults.

Separate network access from Windows sign-in

A network-share warning can appear before the next restart, but it does not establish why the controller later requests an administrator password. A malformed packet is not a sound diagnosis. Windows normally handles bad packets within the network stack; share access depends on account credentials, permissions, name resolution, reachability, and stored sessions.

After regaining access, check the original network symptom in this order:

1. Confirm that WinMax opens locally before testing any mapped drive.
2. Read the mapped-drive letter and its target path. One VM10Ui installation used an H: mapped drive, but that letter is not a universal Hurco setting.
3. Open the target while signed in under the controller's normal account.
4. If Windows requests approval or credentials, test the share account and permissions. Do not change the controller administrator password merely to repair a share.
5. Restart only after documenting each network change and confirming how the controller will sign in again.

If WinMax works but the share does not, that is not a WinMax startup fault. Repair the path, credentials, or permissions without disturbing the control application.

Recover access without damaging the control

If the known candidates fail, choose the recovery path by risk. Start with the controller's documented recovery process or Hurco support. CNC controllers can depend on a specific Windows image, startup account, services, drivers, and application permissions.

An offline recovery was reported on a VM10Ui: boot from a USB recovery environment and erase the administrator password on the original partition. The machine then returned to normal operation. That result proves the method can restore one installation, but it does not define a safe procedure for every controller image.

1. Record the machine model, displayed account, complete sign-in message, and the networking changes made before restart.
2. Locate the controller backup, recovery media, and machine-specific license information before modifying the Windows account database.
3. Ask Hurco for the approved credential or recovery path for the installed control image.
4. Use offline password modification only under an authorized recovery procedure. Select the controller's Windows partition explicitly; never choose a partition by position alone.
5. After access returns, preserve the existing account profile and startup configuration. Do not rename the account or replace the profile as part of password recovery.

Boot-media password tools can target the wrong partition, invalidate stored credentials, change account protection data, or leave the control unable to start its normal shell. Reinstalling Windows is a poor first fix because it can remove controller-specific software, drivers, configuration, and licensing.

Verify WinMax and the network separately

Do not declare the repair complete at the Windows desktop. Verify the control path first, then the network path.

1. Restart the controller through its normal shutdown and startup sequence.
2. Confirm that the panel passes Windows sign-in without returning to the unexpected password prompt.
3. Open WinMax and confirm that its normal operator interface loads.
4. Check that machine configuration and expected local program storage are present.
5. Test the mapped network location independently. Confirm that directory listing and file access work under the intended account.
6. Perform one more controlled restart. A fix that works only until reboot has not restored the startup session.

Do not enable automatic sign-in, change local security policy, or grant broad share permissions merely to hide the prompt. Those actions can mask the failed account path while weakening the controller and leaving the next restart unpredictable.

FAQ