[FIX] Client License Service (ClipSVC) ‘Service Terminated Unexpectedly’ Error on Windows 10 / 11

Some Windows users are experiencing a weird issue where they’re suddenly unable to open any Windows Store apps (Universal Windows Platform apps). Every time they try to open a Microsoft Store app, they see the following error: “Windows could not start the Client License Service (ClipSVC) service on the LocalComputer (The Specified Module could not be found)”. This problem is reported to occur on Windows 10 and Windows 10. 

Client License Service (ClipSVC) service terminated unexpectedly

Note: CLIPSVC stands for Client License Service, and it’s utilized to give Microsoft Store Applications a licensing support structure. CLIPSVC must be enabled in order for the Windows Store apps to work.

After investigating this particular issue, we realized that there are actually several different fairly similar scenarios that might be ultimately causing this type of error. Here’s a shortlist of potential issues that might be causing this error code:

  • ClipSVC service is disabled – One of the most common causes that might be triggering this error is a scenario in which the main service that’s supposed to handle the licensing support structure for Microsoft apps is disabled. In this case, you should start by ensuring the service is a startup and modify the startup type if necessary.
  • The Windows version is outdated – As it turns out, the vast majority of underlying causes that might trigger this problem on Windows 10 have since been addressed by Microsoft. So if you’re looking for an easy way to fix this problem, the first thing you’ll need to do is trigger an update check via Windows Update and install every pending update.
  • The date & Time is incorrect – According to a lot of affected users, you might expect to deal with this issue in scenarios where the licensing support check fails because the date & time expected by the validation server is different than the one on your system. If this scenario is applicable, all you need to do is ensure that the date & time on your computer is correct.
  • Bad updates are installed – Keep in mind that if you’re experiencing this issue on Windows 10, there are two bad updates that are most likely responsible for the failure of several Microsoft apps with this error. In order to fix this problem, all you need to do is uninstall the two problematic updates and use a utility to hide them from WU so that they don’t get reinstalled again. 
  • Missing hotfix update (KB5015020) – Keep in mind that there are scenarios where your Windows version will not automatically install the hotfix that Microsoft released for this particular problem. In this case, you can install the missing update (KB5015020) yourself from the Microsoft Update Catalog.
  • Store Apps Inconsistency – In case you only experience this problem with several Windows Store apps, you could actually be dealing with an inconsistency that you might be able to resolve automatically using the Windows Store Apps Troubleshooter. Simply run the troubleshooter and apply the recommended fix. If the issue is not resolved automatically, also try repairing, resetting, or reinstalling the Microsoft Store. 
  • Certain Store apps are de-registered – Keep in mind that there are certain UWP (Universal Windows Platform) apps that have a tendency to de-registering themselves after Windows infrastructure updates. If this is the cause of the issue, you can rectify the problem by re-registering your entire fleet of Store apps.
  • Corrupted local Store cache – Another scenario that you should troubleshoot as well as some kind of corruption that is currently affecting the Local cache of Microsoft Store. If this scenario is applicable, simply clear the local cache using the WSReset.exe utility or do it the manual way. 
  • Corrupted registry data – As it turns out, there is a certain scenario in which an infrastructure update on Windows 10 ended up causing this problem after breaking certain registry keys. If this scenario is applicable, you can get the issue resolved by replacing your corrupted reg. keys with healthy equivalents. 
  • System File corruption – If none of the other methods have worked for you, the last thing you should troubleshoot is a potential corruption issue that is currently affecting your Windows installation. In this case, the best thing you could do is deploy a repair install or go for a clean install if you don’t mind losing personal data from your drive. 

Now that we went over every potential cause that might be causing this problem, let’s go over every potential fix that was verified by at least one other affected user that was experiencing this problem on Windows 10 or Windows 11. 

1. Start the CLIPSVC service manually

A scenario in which the principal service that is meant to handle the license support structure for Microsoft programs is deactivated is one of the most typical reasons for this problem. In this scenario, you should verify that the service is a startup and, if necessary, change the startup type.

You can do all of this from the Services screen. Several affected users have confirmed that this method allowed them to ensure that the CLIPSVC service was correctly configured and available as a dependency when needed.

Here’s what you need to do to start the CLIPSVC service manually:

  1. Press Windows key +  R to open up a Run dialog box. 
  2. Next, type ‘service.msc’ inside the Run dialog box, then press Ctrl + Shift + Enter to open up the Services screen with admin access. 
    Accessing the Services screen
  3. At the User Account Control window, click Yes to grant admin access. 
  4. Once you’re inside the Services screen locate the Client License Service (ClipSVC) entry. 
  5. After you locate the correct service, double-click on the correct service.
    Accessing the ClipSVC service
  6. From the properties screen of the ClipSVC service, go to the General, then Set the Startup type to Manual, then click on Start to launch the service. 
  7. Repeat the action that was previously causing the error and see if the problem is now fixed. 

If you’re still experiencing the “Windows could not start the Client License Service (ClipSVC) service’ error, move down to the next method below.

2. Update Windows build to the latest

As it turns out, Microsoft has addressed the great majority of underlying factors that could cause this issue on Windows 10. So, if you’re seeking a quick resolution for this issue, the first thing you should do is run a Windows Update check and apply any pending updates.

Note: This issue arose as a result of this change, which prevented some services from indirectly authenticating machine accounts on clients (required when performing certain tasks in Store).
Microsoft has since developed a fix for the issue, which you may apply by simply installing all pending updates from Windows Update.

So, before you do anything else, check the Windows Update window for any outstanding updates (especially cumulative and feature upgrades). If Microsoft has recently announced a fix for this problem, installing all pending updates should address the problem right away.

If you find yourself in this scenario, follow these procedures to complete the installation of all pending Windows Updates on your computer:

  1. To open the Run dialog box, press the Windows key + R.
  2. Type ‘ms-settings:windowsupdate’ and hit Enter once inside the Run box to open the Run dialog box.
    Access the Windows Update component
  3. Select Yes to grant admin access when the User Account Control prompts you.
  4. On the Windows Update screen, scroll down to the right-hand pane and click Check for Updates.
    Checking for updates
  5. Once the first scan is complete, apply all pending updates (as advised) and restart your computer as needed.
  6. After your computer has restarted, perform the action that caused the “Windows could not start the Client License Service (ClipSVC) service” error to check if the issue has been resolved.

If the problem persists, proceed to the next method listed below.

3. Uninstall KB5013942 & KB5011831 updates

Keep in mind that if you’re having this problem on Windows 10, two faulty updates are almost certainly to blame for the failure of multiple Microsoft programs with this message. To resolve this issue, just uninstall the two problematic updates and use a tool to conceal them from Windows Update so that they are not reinstalled.

Several affected users have reported that the problem was entirely resolved after they used the Windows Uninstall & Hide update to remove the KB5013942 & KB5011831 updates from their PC.

Here’s what you need to do:

  1. To launch the Run dialog box, press Windows key + R. To launch the Programs and Features menu, put ‘appwiz.cpl’ into the Run prompt and hit Enter.
    Open the Programs and Features menu
  2.  From the vertical menu in the top-left corner of the screen, select View installed updates once you’re within Programs and Features.
    View Installed updates
  3. Right-click the KB5013942 update in the Installed Updates pane and select Uninstall from the context menu.
    Uninstalling the problematic updates
  4. Confirm the uninstallation of the KB5013942 update, then repeat step 3 with KB5011831 if you have it installed too.

Now that both updates are uninstalled, the next thing you should do is ensure that your OS doesn’t install them over once again. You can prevent this from happening by using the Microsoft Show or hide troubleshooter:

  1. To get started, go to the Microsoft Show or Hide troubleshooter’s official download website. The download should start automatically.
  2. Once the download is complete, open the .diagcab file and choose Advanced at the first window. Then, before clicking Next, select the option to Apply Repairs Automatically from the drop-down menu.
  3. Wait for the application to finish scanning your system to see which pending updates have yet to be installed. Select Hide Updates from the drop-down option on the following screen. 
    Hiding the updates

    4. On the next screen, check the box next to the faulty update, then click Next to hide it from Windows Update.

  4. Makes sure that both updates (KB5013942 & KB5011831) are hidden from your OS view before restarting your PC.

If you didn’t have these updates installed and this method was not applicable, follow the next method below. 

4. Install KB5015020 update from the Microsoft Update Catalog

Keep in mind that your Windows version may or may not automatically install the Microsoft update for this issue. You can manually install the missing update (KB5015020) from the Microsoft Update Catalog in this scenario.

If this scenario sounds like it might apply to you, start by downloading the KB5015020 update for Windows 11 from this official download MSU link.

After the download is finished, go to the folder where you downloaded the MSU hotfix, right-click it, and select Run as administrator.

Run the Hotfix as an administrator

After that, follow the on-screen directions to complete the hotfix installation, and then restart your computer.

Note: If you installed this hotfix, the “Windows could not start the Client License Service (ClipSVC) service’ error should have been resolved.

If the problem persists, proceed to the next method below.

5. Run the Store Apps Troubleshooter

If an automated repair strategy has already been used to fix the “Windows could not start the Client License Service (ClipSVC) service” error, then the Windows Store Apps Troubleshooter should help you swiftly resolve the issue.

Keep in mind that the principal store component has a set of requirements that all native apps operating on the Universal Windows Platform (UWP) must meet (Microsoft Store).

In some cases (after a bad update, after some type of file corruption), you can expect these shared dependencies to become corrupted and affect the app retrieval process; in these cases, the best course of action is to run the Windows Apps Troubleshooter and let the automated repair component take care of the problem.

Note: If a recognizable scenario is detected, the Windows Apps Troubleshooter provides a repair component with a ton of automated repair options that can be applied.

Use the processes below to run the Windows App Troubleshooter and apply the recommended remedy to repair any shared dependencies if you haven’t previously done so:

  1. To open the Run dialog box, press the Windows key + R.
  2. Then, in the text box, type ‘ms-settings:troubleshoot’ and press Enter to open the Settings menu’s Troubleshooting tab.
    Accessing the troubleshoot menu
  3. Go to the Troubleshoot window’s right-hand pane, then pick Other troubleshooters at the bottom of the screen.
  4. In the dedicated Other Troubleshooters menu, go all the way to the bottom of the page and click the Run option associated with Windows Store Apps.

    Running the troubleshooter
  5. Once you’ve launched the Windows Store App troubleshooter, wait until the initial scan is complete to see if a potential solution has been discovered.
  6. If a repair method is offered, choose it and then click Apply this Fix.

    Apply the recommended fix

    Note: Depending on the type of repair specified, you may be required to complete the task by following a series of manual instructions.

  7. After the repair has been successfully implemented, reboot your Windows PC to see if the problem has been resolved.

If you’re still having trouble getting around the “Windows could not start the Client License Service (ClipSVC) service” error, try the following way down below.

6. Set the Correct Time & Date

According to many impacted users, you can encounter this problem when the license support check fails because the validation server’s expected date and time differ from the one on your machine. If this scenario applies to you, all you need to do is make sure your computer’s date and time are correct.

As it turns out, if your local system’s time and date settings change from those expected by the Microsoft Store server, you may be unable to access personalized listings of Windows Store apps and games – you will be able to get to the home screen, but not to the dedicated page.

If you find yourself in this situation, the solution is simple: adjust the date and time to the correct numbers so that the MS server does not object to your connection.

Follow the steps below if you don’t know how to set the date and time to the correct values:

  1. Make sure your computer is linked to the internet.
  2. To launch a Run dialog box, hit Windows key + R.
  3. To access the Date & Time panel, type ‘timetable.cpl’ into the run box that just appeared and hit Enter.
    Opening the Time & Date screen
  4. Once you’re in the Date & Time box, go to the Internet Time tab and then click Change settings.

    Change the date & time
  5. When the User Account Control (UAC) prompts you, click Yes to grant admin access.
  6. Begin by ticking the box next to Synchronize with an Internet time server in the Internet Time settings.
    Synchronizing the date & time server
  7. Finally, select time.windows.com as the server and click Update Now.
  8. Once the setting is in place, go back to the main Date & Time page, select Change time zone, and double-check that you’re in the correct timezone while keeping your current geolocation in mind.
  9. After that, click Change date and time to confirm that the date has been successfully sent.
    Date & Time settings
  10. Finally, make your changes and then select Apply to make the changes permanent.
  11. Restart your computer and wait for it to finish the next startup.
  12. After your Windows 11 machine has restarted, go to the Microsoft Store and try to open the same dedicated app listing that caused the store component to crash. The issue should now be rectified if the problem was caused by the date and time values.

If the issue is still not fixed, move down to the next method below. 

7. Re-Register the Store app

According to some impacted customers, this issue can also occur if the Windows Store software has been de-registered. If this is the case, re-registering the Windows Store app for all accounts will fix the problem.

In this case, you should be able to fix the problem by using Powershell to re-register the Store app. This solution has been confirmed to work by several Windows 11 and Windows 10 customers who were experiencing the ClipSVC issue.

Using an elevated Powershell window, here’s how to re-register the Store app:

  1. Press the Windows key + R to open the Run dialog box.
  2. In the newly launched window, type ‘powershell’ and hit Ctrl + Shift + Enter to start an elevated Powershell window.
    Accessing the Powershell window
  3. Click Yes to allow the UAC (User Account Control) window to open with administrative privileges.
  4. To re-register the Windows Store component, execute the following command into the elevated Powershell window and click Enter:
    Get-AppXPackage *WindowsStore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  5. After executing the command, restart your computer to verify if the problem is resolved on the next system startup.

If the ClipSVC error recurs, move on to the next option listed below.

8. Repair, Reset, or Reinstall the Microsoft Store

If you only have this problem with a few Windows Store apps, it’s possible that you’re dealing with an inconsistency that the Windows Store Apps Troubleshooter can automatically correct. Simply run the troubleshooter and follow the instructions. If the problem doesn’t go away on its own, try repairing, resetting, or reinstalling the Microsoft Store.

You should expect this problem to develop as a result of corruption in the Microsoft Store cache or the Microsoft Store installation files, depending on your situation. In this case, you should try to repair the Store Component first before resorting to a reset approach if the repair fails.

Many users have reported that this update was the only thing that let them get rid of the annoying ‘We can’t get your tasks right now’ message.

Note: Even if this issue is caused by a Microsoft Store component, the data stream is still handled by the Microsoft Store Service. This is why, in this case, fixing or resetting the Microsoft Store app may be beneficial.

We propose forcing the Store to repair first, then using the reset feature as a safeguard. You can also try reinstalling the Microsoft Store if the first two options don’t work.

This is what you must do in order to perform these repairs:

  1. Make sure the Microsoft Store program isn’t running in the background and is shut off.
  2. Press Windows key + I to open the Windows Settings menu.
  3. Select Apps from the left-hand vertical menu, then Installed apps from the right-hand menu, from the Settings screen.
    Access the Installed Apps menu

    Note: If you don’t see the side menu by default, click the action button (top-left corner of the screen).

  4. Using the search option at the top, look for ‘Microsoft Store’ in the Installed Apps menu.
  5. Select Advanced Options from the drop-down menu on the action icon.
    advanced-options-microsoft-store
    Microsoft store advanced options
  6. In the Microsoft Store’s Advanced Options menu, go down to the Reset tab and click the Repair button.
  7. When the confirmation window displays, click Repair to confirm the operation and then wait for it to complete
     
  8. After you’ve performed the Microsoft Store repair option, restart your computer to see if the issue has been addressed.
  9. If the problem remains, follow the steps above but instead of selecting Reset, execute a reset operation.
    Repair or Restart Microsoft Store
  10. Once both of these steps have been completed, recreate the action that was causing the error and see if the problem is now fixed.

If you’re still experiencing the same ‘Windows couldn’t start the Client License Service (ClipSVC) service’ error, move down to the next method below. 

9. Reinstall Microsoft Store

If the reset and repair procedures above didn’t allow you to fix the ‘Windows couldn’t start the Client License Service (ClipSVC) service’ error, one final way to make sure that this problem is not caused by a corrupted Microsoft Store instance is to reinstall the entire component.

In order to do this, you will need to do this from an elevated Powershell window. Several affected users have confirmed that this problem went away entirely after they followed the instructions below.

Here’s what you need to do:

  1. Make sure that the Windows Store component is closed and not running in the background.
  2. Press Windows key + R to open up a Run dialog box. 
  3. Next, type ‘powershell’ inside the Run dialog box, then press Ctrl + Shift + Enter to open up an elevated Powershell window.
    Open up an elevated PowerShell window
  4. At the User Account Control, click Yes to grant admin access. 
  5. Once you’re inside the elevated Powershell window, paste (or type) the following command and press Enter to effectively reinstall the Microsoft Store:
    Get-AppxPackage -allusers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
  6. Once the command has been ranked successfully, reboot your PC and see if the problem is now fixed.

If you’re still dealing with issues related to the ClipSVC service, move down to the next method below. 

10. Deploy a WSReset.exe procedure

The most common reason for this type of behavior with the Microsoft Store on Windows 11 and Windows 10 is probably bad cached data.

Despite the fact that cached files are required for your Microsoft Store installation (they increase reaction times and overall speed), removing them will not cause any underlying issues with the store component – after all, you can’t utilize Windows Store properly if you have this issue.

If you don’t want to do it manually, you can use WSReset.exe, a troubleshooting tool, to reset and clear the Windows Store without altering your account settings or uninstalling your installed apps.

Note: If you want to go for the manual route, follow the next method below.

All you have to do is run this tool in an administrative environment, and all damaged cached data that may be influencing Windows Store behavior should be deleted.

Follow the steps below to remove the Windows Store cache and refresh the Store component using the WSreset.exe application:

  1.  Press the Windows key + R to open the Run dialog box.
  2. In the run box, type ‘wsreset.exe’ into the text prompt, then press Ctrl + Shift + Enter to run the tool as an administrator.
    Deploying a wsreset operation
  3. When the User Account Control prompt appears, click Yes to grant admin access.
  4. The software will run automatically inside the elevated command prompt and delete the
  5. The window will close within 10 seconds or so (depending on your storage capacities), and Microsoft Store will open automatically.
  6. If the store doesn’t open automatically, reopen the Microsoft Store manually and perform the action that caused the error to appear to see if the issue has been addressed.

If you’re still getting the ‘Windows couldn’t start the Client License Service (ClipSVC) service’ issue, try the next solution below.

11. Clear the Local cache of Microsoft Store

If the manual way above of clearing the cache wasn’t effective in your case (or you want to avoid it, you can always go for the automated way.

According to many affected users, you can expect to run into this issue if the Microsoft Store’s LocalCache folder has broken data that prevents waiting for updates from being installed. Manually emptying the LocalCache folder should cure the problem in this case.

If you still can’t get the problem to go away (even after doing the wsreset method), follow the steps following to manually remove the Windows Store cache folder:

  1. Ensure that the Windows Store component is completely turned off.
  2. Press Windows key + R to open the Run dialog box.
  3. Type ‘%APPDATA%’ into the Run box’s text field, then press Ctrl + Shift + Enter to reveal the hidden AppData folder.
    Open up the AppData folder
  4. Open the AppData folder and go to the following location:
    C:\Users\User_name\AppData\Local\Packages \Microsoft.WindowsStore_8wekyb3d8bbwe\
  5. Select Delete from the pop-up menu when you right-click on LocalCache.
    Delete the local WS cache

    Important: Note that the Store component will regenerate this folder automatically the next time you run the program, so deleting it will have no underlying consequences.

  6. Relaunch the Microsoft Store after deleting the LocalCache folder to determine if the error has been resolved.

If the ‘Windows couldn’t start the Client License Service (ClipSVC) service’ error persists, proceed to the next method below.

12. Merge a healthy Registry equivalent

As it turns out, there is a specific case in which a Windows 10 infrastructure upgrade caused this issue by breaking particular registry keys. If this is the case, you can fix the problem by replacing the corrupted registry keys with healthy replacements.

The way to do this is to create a Registry Script, then merge it with the equivalent on your system in order to ensure that the ClipSVC has all the required services in order to run. 

Note: Before you start with the operation below, our advice is to create a system restore point first. This will allow you to revert back to a healthy Registry state in case something goes wrong with this operation.

Once you have the backup in place, follow the instructions below to merge a healthy Registry equivalent with the existing one on your PC;

  1. Press Windows key + R to open up a Run dialog box.
  2. Next, type ‘notepad’ inside the Run dialog box, then press Ctrl + Shift + Enter to open up up the Notepad with admin access. 
     
    Open Notepad
  3. At the User Account Control, click Yes to grant admin access. 
  4. Inside the elevated Notepad box, paste the following code: 
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC]
    
    "DisplayName"="@%SystemRoot%\\system32\\ClipSVC.dll,-103"
    
    "ErrorControl"=dword:00000001
    
    "ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
    
      74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
    
      00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
    
      6b,00,20,00,77,00,73,00,61,00,70,00,70,00,78,00,00,00
    
    "Start"=dword:00000003
    
    "Type"=dword:00000020
    
    "Description"="@%SystemRoot%\\system32\\ClipSVC.dll,-104"
    
    "DependOnService"=hex(7):72,00,70,00,63,00,73,00,73,00,00,00,00,00
    
    "ObjectName"="LocalSystem"
    
    "ServiceSidType"=dword:00000001
    
    "RequiredPrivileges"=hex(7):53,00,65,00,43,00,72,00,65,00,61,00,74,00,65,00,47,\
    
      00,6c,00,6f,00,62,00,61,00,6c,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,\
    
      67,00,65,00,00,00,53,00,65,00,43,00,68,00,61,00,6e,00,67,00,65,00,4e,00,6f,\
    
      00,74,00,69,00,66,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,\
    
      65,00,00,00,53,00,65,00,53,00,79,00,73,00,74,00,65,00,6d,00,45,00,6e,00,76,\
    
      00,69,00,72,00,6f,00,6e,00,6d,00,65,00,6e,00,74,00,50,00,72,00,69,00,76,00,\
    
      69,00,6c,00,65,00,67,00,65,00,00,00,00,00
    
    "FailureActions"=hex:84,03,00,00,00,00,00,00,00,00,00,00,01,00,00,00,14,00,00,\
    
      00,00,00,00,00,00,00,00,00
    
    "LaunchProtected"=dword:00000002
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\Parameters]
    
    "InactivityShutdownDelay"=dword:0000012c
    
    "RefreshRequired"=dword:00000002
    
    "ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
    
      00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
    
      43,00,6c,00,69,00,70,00,53,00,56,00,43,00,2e,00,64,00,6c,00,6c,00,00,00
    
    "ServiceDllUnloadOnStop"=dword:00000001
    
    "ProcessBiosKey"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\Security]
    
    "Security"=hex:01,00,14,80,b8,00,00,00,c4,00,00,00,14,00,00,00,30,00,00,00,02,\
    
      00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
    
      00,00,02,00,88,00,06,00,00,00,00,00,14,00,ff,01,02,00,01,01,00,00,00,00,00,\
    
      05,12,00,00,00,00,00,18,00,fd,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
    
      20,02,00,00,00,00,14,00,9d,01,02,00,01,01,00,00,00,00,00,05,04,00,00,00,00,\
    
      00,18,00,94,00,00,00,01,02,00,00,00,00,00,0f,02,00,00,00,01,00,00,00,00,00,\
    
      14,00,9d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,00,00,14,00,14,00,00,\
    
      00,01,01,00,00,00,00,00,05,0b,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00,\
    
      01,01,00,00,00,00,00,05,12,00,00,00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\TriggerInfo]
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\TriggerInfo\0]
    
    "Type"=dword:00000006
    
    "Action"=dword:00000001
    
    "GUID"=hex:67,d1,90,bc,70,94,39,41,a9,ba,be,0b,bb,f5,b7,4d
    
    "Data0"=hex:36,00,34,00,44,00,31,00,44,00,30,00,34,00,35,00,2d,00,46,00,36,00,\
    
      37,00,35,00,2d,00,34,00,36,00,30,00,42,00,2d,00,38,00,41,00,39,00,34,00,2d,\
    
      00,35,00,37,00,30,00,32,00,34,00,36,00,42,00,33,00,36,00,44,00,41,00,42,00,\
    
      00,00
    
    "DataType0"=dword:00000002
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\TriggerInfo\1]
    
    "Type"=dword:00000007
    
    "Action"=dword:00000001
    
    "GUID"=hex:16,28,7a,2d,5e,0c,fc,45,9c,e7,57,0e,5e,cd,e9,c9
    
    "Data0"=hex:75,08,bc,a3,21,07,85,41
    
    "DataType0"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\TriggerInfo\2]
    
    "Type"=dword:00000007
    
    "Action"=dword:00000001
    
    "GUID"=hex:16,28,7a,2d,5e,0c,fc,45,9c,e7,57,0e,5e,cd,e9,c9
    
    "Data0"=hex:75,10,bc,a3,21,07,85,41
    
    "DataType0"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\TriggerInfo\3]
    
    "Type"=dword:00000007
    
    "Action"=dword:00000001
    
    "GUID"=hex:16,28,7a,2d,5e,0c,fc,45,9c,e7,57,0e,5e,cd,e9,c9
    
    "Data0"=hex:75,18,bc,a3,21,07,85,41
    
    "DataType0"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\TriggerInfo\4]
    
    "Type"=dword:00000007
    
    "Action"=dword:00000001
    
    "GUID"=hex:16,28,7a,2d,5e,0c,fc,45,9c,e7,57,0e,5e,cd,e9,c9
    
    "Data0"=hex:75,20,bc,a3,21,07,85,41
    
    "DataType0"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\TriggerInfo\5]
    
    "Type"=dword:00000007
    
    "Action"=dword:00000001
    
    "GUID"=hex:16,28,7a,2d,5e,0c,fc,45,9c,e7,57,0e,5e,cd,e9,c9
    
    "Data0"=hex:75,28,bc,a3,21,07,85,41
    
    "DataType0"=dword:00000001
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClipSVC\TriggerInfo\6]
    
    "Type"=dword:00000007
    
    "Action"=dword:00000001
    
    "GUID"=hex:16,28,7a,2d,5e,0c,fc,45,9c,e7,57,0e,5e,cd,e9,c9
    
    "Data0"=hex:75,30,bc,a3,21,07,85,41
    
    "DataType0"=dword:00000001
  5. Once the code is successfully pasted inside the notepad, go to the ribbon at the top and click on File > Safe As
    Saving the code as .reg file
  6. From the Save As Menu, change the Save as type to All Files, then name it however you want, but make sure you end it with the ‘.reg’ extension. 
    Creating a reg file
  7. Next, right-click on the newly created .reg file and choose Run as Administrator
  8. After the .reg hey ran successfully, reboot your PC and see if the problem is now fixed. 

If the same ‘Windows couldn’t start the Client License Service (ClipSVC) service‘ error is still occurring as the Client License Service refuses to start, move down to the next method below. 

13. Perform a Repair Install

If you’ve followed every method in this article and are still getting the ‘Service Terminated Unexpectedly’ error, the issue is almost certainly caused by system file corruption that can’t be fixed using traditional methods.

In this instance, refreshing every Windows component is the best approach to fix the problem without needing a full OS rebuild (including boot data).

There are two alternatives available to you:

  • Repair Install – This is a more time-consuming technique (also known as in-place repair). It necessitates the use of installation media, but the benefit is that you can preserve all of your personal files (including personal movies, games, apps, and even some user preferences) without having to back them up beforehand.
  • Clean installation – This is the simplest method. You don’t need any installation disk, and you can start it right from the Windows 10 start menu. If you don’t back up your data before starting this procedure, you will lose everything.
Kamil Anwar
Kamil is a certified MCITP, CCNA (W), CCNA (S) and a former British Computer Society Member with over 9 years of experience Configuring, Deploying and Managing Switches, Firewalls and Domain Controllers also an old-school still active on FreeNode.
Back to top button

Expert Tip

[FIX] Client License Service (ClipSVC) ‘Service Terminated Unexpectedly’ Error on Windows 10 / 11

If the issue is with your Computer or a Laptop you should try using Restoro which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption. You can download Restoro by clicking the Download button below.

Download Now

I'm not interested