![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 81%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECT%3C/text%3E%3C/svg%3E)
Hello Handian,
Thank you for posting question on Microsoft Windows Forum!
Well! The plausible explanation to your query is that when users are prompted for credentials upon accessing \smbserver and only see a PIN option, it is usually caused by Windows defaulting to a "Passwordless Experience". In newer builds of Windows 10 and 11, Microsoft actively pushes users away from traditional passwords. If the endpoint is configured for a passwordless experience (either by default during setup or enforced via Intune/MDM policies), Windows hides the standard password credential provider across the operating system. Including in the Windows Security network prompt.
On the other hand, Windows SMB shares do not actually authenticate with a PIN. The PIN you see is part of Windows Hello local sign‑in, not a credential usable for network authentication. SMB requires your full account password or a stored credential, which is why there is no “password option” when you log in with a PIN.
Based on the above information, the endpoint does not show a password option because PIN sign‑in is a local convenience feature, not a network credential. To access SMB, you must use your actual password or configure Credential Manager.
Hope the answer is helpful to address your concerns. If it is. It is appreciated to consider clicking "Accept Answer".