Conflict with installing service fabric runtime 10.1.2493.9590

Question

I'm trying to install the service fabric runtime using this command:

.\MicrosoftServiceFabric.10.1.2493.9590.exe /force /accepteula 

I am getting this error message:

5/29/2025 10:08:24 PM,Error,Unable to install Service Fabric Runtime using C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code\InstallFabric.ps1. ExitCode: 1. Find additional logs at: C:\Windows\TEMP\FabricSetupLog_638840413843119438.log.

The linked log shows:

I've also tried running: & 'C:\Program Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code\InstallFabric.ps1' -FabricRootIsPreInstalled -AcceptEULA

The script runs but fails during the driver installation phase with the following error:

Error 0x800704fb while installing driver LeaseLayer
DriverInstallManager::Install failed with error 0x800704fb

This error appears to correspond to: “A system shutdown is in progress.”

Are there any known workarounds or additional steps to resolve this issue?

I appreciate any help.

Answer 1

Hello Jania,

Thank you for posting your question in the Microsoft Q&A forum. 

The Service Fabric runtime installation failure with error 0x800704fb ("A system shutdown is in progress") typically occurs due to pending system operations or driver conflicts during setup. To resolve this, first check for pending reboots (run shutdown /a to abort any unintended shutdowns) and ensure Hyper-V or Containers features are fully installed, as Service Fabric depends on these. 

If the issue persists, manually install the LeaseLayer driver by: 

• Extracting the driver (LeaseLayer.inf) from the Service Fabric installer. 
• Run below powershell command: 

     *pnputil /add-driver "C:\path\to\LeaseLayer.inf" /install*   
  

• Disabling driver signature enforcement temporarily (bcdedit /set testsigning on). 

Alternatively, clean boot Windows to eliminate third-party service interference, or deploy via ARM template to bypass local setup quirks. For persistent failures, review Event Viewer logs under System for driver-related errors. 

 Reference documentation you may review - https://learn.microsoft.com/en-us/azure/service-fabric/

If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated. 

Answer 2

Hello Jania, I believe you are trying to install this on your office MS imaged laptop and it has a corporate policy enabled and that is the blocker. From the installation logs and error messages, the issue seems to stem from Memory Integrity (Core Isolation) being enabled and locked via Group Policy, which blocks the LeasLayr.sys driver from loading. The machine has Memory Integrity (Core Isolation) enabled, and it's locked via Group Policy (This setting is managed by your administrator). As a result, Windows is blocking the Service Fabric kernel driver LeasLayr.sys from loading — which causes the installation to fail.

On your laptop, if you go to windows security-> core isolation -> you will memory integrity is on

If you spin up a windows VM free from these corporate restrictions on Azure, you will see it is working fine. If you want you can even test it out on your personal laptop. It will work.