Skip to main content
The Website Services team at NHS England are testing early designs to understand how you find information. Your views will help us check our ideas work. Sign up to take part in our user research.

News

Smartcard Connect startup and load time issues

Help for users experiencing long loading times for Smartcard Connect.

Some organisations may experience long loading times for Smartcard Connect when starting or restarting Windows 11 machines.

This is because Windows 11 sometimes delays launching start‑up programs until the computer's CPU is idle, which can cause NHS Credential Management and Smartcard Connect to start late after login.

What to do

The following steps using the Windows registry tell Windows to launch these programs immediately:

  1. Press Windows Key + R, type regedit, and press Enter.
  2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer.
  3. Right-click Explorer in the left-hand panel, hover over New, and select Key.
  4. Name the new key Serialize.
  5. Right-click in the right-hand panel, hover over New, and select DWORD (32-bit) Value.
  6. In the name field for the new value, type StartupDelayInMSec. Leave Data as the default value (0).
  7. Right-click in the right-hand panel again, hover over New, and select DWORD (32-bit) Value.
  8. In the name field for the second new value, type WaitForIdleState. Leave Data as the default value (0).

StartupDelayInMSec=0 removes the normal startup-app delay. WaitForIdleState=0 explicitly prevents waiting for the idle state. Microsoft explains this configuration in a recent Microsoft Q&A response.

For these changes to come into effect you will need to reboot the machine or log out and in again.

About these registry changes

These changes only affect startup applications managed by Explorer - they will not override any start-up settings set locally. If you have any local settings that affect the start-up of NHS Credential Management and Smartcard Connect you will need to remove them for the registry changes above to be successful. This includes:

  • a scheduled task configured with 'Start the task only if the computer is idle' -  you'll need to remove this from the task itself (see Microsoft documentation)
  • a Windows service configured as 'Automatic (Delayed Start)' - you'll need to change it to 'Automatic' (see Microsoft documentation)
  • an application's own internal startup delay
  • Group Policy logon-script processing delays



Last edited: 12 November 2026 11:50 am