How to Fix “The Microsoft iSCSI Service Is Not Running” on Windows 11

The Microsoft iSCSI Initiator Service allows Windows to connect to remote storage devices over an IP network using the iSCSI (Internet Small Computer Systems Interface) protocol. It is commonly used in enterprise environments for accessing SAN (Storage Area Network) storage, Hyper-V clusters, SQL Server deployments, backup solutions, and other applications that rely on shared storage. If the service isn’t running, Windows won’t be able to discover or connect to iSCSI targets, resulting in storage connectivity issues.

The “The Microsoft iSCSI service is not running” error usually appears when opening the iSCSI Initiator or attempting to connect to an iSCSI target. This can happen due to the service being disabled, incorrect startup settings, corrupted system files, dependency service failures, Group Policy restrictions, outdated storage drivers, or problems introduced by recent Windows updates. In some cases, third-party security software or damaged Windows components can also prevent the service from starting.

Fortunately, there are several ways to resolve the problem. In this guide, we’ll show you how to fix the Microsoft iSCSI service is not running error on Windows 11 and Windows Server.

How to Fix “The Microsoft iSCSI Service Is Not Running”

Work through the following solutions in order. After each method, check whether the Microsoft iSCSI Initiator Service starts successfully.

1. Start the Microsoft iSCSI Initiator Service

The service may simply be stopped.

To start it:

1. Press Windows + R, type services.msc, and press Enter.
2. Locate Microsoft iSCSI Initiator Service.
3. Double-click the service.
4. Click Start.
5. Click Apply and OK.

If the service starts successfully, reopen the iSCSI Initiator and verify that the error is gone.

2. Set the Service Startup Type to Automatic

If the startup type is set to Disabled or Manual, the service may not start automatically after reboot.

To change it:

1. Open Services.
2. Double-click Microsoft iSCSI Initiator Service.
3. Set Startup type to Automatic.
4. Click Apply.
5. Click Start if the service isn’t already running.
6. Restart your computer.

This ensures the service starts whenever Windows boots.

3. Start the Service Using PowerShell

If the Services console doesn’t work, PowerShell can start the service directly.

To do this:

1. Open Windows PowerShell as an administrator.
2. Run the following command:

Start-Service MSiSCSI

3. Verify the service status:

Get-Service MSiSCSI

If the status shows Running, the service has started successfully.

4. Check Service Dependencies

The iSCSI service depends on several Windows services.

To verify:

1. Open Services.
2. Open the properties of Microsoft iSCSI Initiator Service.
3. Go to the Dependencies tab.
4. Ensure all required services are running.
5. Start any dependency services that are stopped.

A stopped dependency can prevent the iSCSI service from starting.

5. Restart the Storage Services

Restarting related services can refresh Windows storage components.

To do this:

1. Open Services.
2. Restart the Microsoft iSCSI Initiator Service.
3. Restart other related storage services if applicable.
4. Close the Services window.
5. Test the iSCSI connection again.

This refreshes communication between Windows and storage components.

6. Update Storage and Network Drivers

Outdated drivers can interfere with iSCSI connectivity.

To update them:

1. Press Windows + X and select Device Manager.
2. Expand Storage controllers.
3. Update storage controller drivers.
4. Expand Network adapters.
5. Update your network adapter drivers.
6. Restart the computer.

Updated drivers improve compatibility with iSCSI storage.

7. Install the Latest Windows Updates

Microsoft frequently releases fixes for storage and networking components.

To update Windows:

1. Open Settings > Windows Update.
2. Click Check for updates.
3. Install all available updates.
4. Restart your computer.
5. Test the iSCSI service again.

Keeping Windows updated helps prevent service-related issues.

8. Verify Firewall Settings

Firewall rules may block communication with iSCSI targets.

To check:

1. Open Windows Security.
2. Go to Firewall & network protection.
3. Ensure the necessary firewall rules for iSCSI are enabled.
4. Verify that TCP port 3260 is not blocked.
5. Retry the connection.

Proper firewall configuration is essential for successful iSCSI communication.

9. Check Group Policy Settings

In managed environments, Group Policy may restrict storage services.

To verify:

1. Open the Local Group Policy Editor or review domain policies.
2. Check policies related to system services.
3. Confirm that the Microsoft iSCSI Initiator Service isn’t disabled.
4. Refresh Group Policy.
5. Restart the service.

Policy restrictions can override local service settings.

10. Repair Windows System Files

Corrupted Windows files can prevent services from starting.

To repair them:

1. Open Command Prompt as an administrator.
2. Run the System File Checker (SFC) scan.
3. After it finishes, run the Deployment Image Servicing and Management (DISM) repair commands.
4. Restart the computer.
5. Try starting the iSCSI service again.

Repairing Windows files resolves many service-related issues.

11. Check the Event Viewer Logs

Event Viewer can provide more information about why the service fails.

To view the logs:

1. Press Windows + X and select Event Viewer.
2. Expand Windows Logs.
3. Open System.
4. Look for errors related to MSiSCSI or the Service Control Manager.
5. Review the error details for troubleshooting clues.

The event logs often identify the underlying cause of the failure.

12. Reinstall the iSCSI Feature (Windows Server)

If you’re using Windows Server and the service remains corrupted, reinstalling the feature may help.

To do this:

1. Open Server Manager.
2. Select Manage > Remove Roles and Features if the feature is installed separately.
3. Restart the server if prompted.
4. Add the required storage features again.
5. Restart the server.
6. Test the Microsoft iSCSI Initiator Service.

Reinstalling the feature restores missing or damaged components.

Conclusion

The “The Microsoft iSCSI Service Is Not Running” error typically occurs because the Microsoft iSCSI Initiator Service is stopped, disabled, or unable to start due to dependency failures, corrupted system files, driver issues, or Windows configuration problems. In most cases, starting the service, setting it to Automatic, verifying dependencies, and updating Windows or storage drivers will resolve the issue.

If the problem persists, review Event Viewer logs, check firewall and Group Policy settings, repair Windows using SFC and DISM, or reinstall the iSCSI feature on Windows Server. By following the troubleshooting methods in this guide, you should be able to restore the Microsoft iSCSI Initiator Service and reconnect to your iSCSI storage devices successfully on Windows 11 or Windows Server.