Wsl: Error - The referenced assembly could not be found

Created on 9 Mar 2019  ·  45Comments  ·  Source: MicrosoftDocs/WSL

I face the following error in powershell.
Enable-WindowsOptionalFeature : The referenced assembly could not be found.
At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
  • ~~~~~~~~~~~~~~~~~

    • CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException

    • FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

If I try to enable the windows feature 'Windows Subsystem for Linux' from control panel, I get the error code 0x80073701. And it redirects me to the page https://support.microsoft.com/en-us/help/2734782/net-framework-3-5-installation-error-0x800f0906-0x800f081f-0x800f0907, which is of no help.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Most helpful comment

sorry, I have the same issue

All 45 comments

Same exact issue here. Any luck?

Been having the same issue, any suggestions?

Same when trying to disable the Linux Subsystem feature
image

Any ideas?

I have the same issue. I assumed it was my company windows admins being evil again, but sounds more like a bug now...

PS C:> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

Enable-WindowsOptionalFeature : The referenced assembly could not be found.
At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
  • ~~~~~~~~~~~~~~~~~

    • CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException

    • FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

I've heard the only way to fix this is to update to 1809 but still I'm not sure that it would be effective or not?!

I've heard the only way to fix this is to update to 1809 but still I'm not sure that it would be effective or not?!

I'm already at 1809 and having the exact same issue as @mjd2012gdg

I've heard the only way to fix this is to update to 1809 but still I'm not sure that it would be effective or not?!

I'm already at 1809 and having the exact same issue as @mjd2012gdg

Actually I have updated to 1809 and it is working fine now.

sorry, I have the same issue

Same issue.

Same issue here

Same here :(

Same here.

Looks like this is just another Microsoft dropped ball...

Hi there! We're looking into this issue internally, in the meantime please try running this command in a command prompt Window with administrator privileges:

DISM /Online /Cleanup-Image /CheckHealth

It may fix your problem while we continue troubleshooting. Thank you all for your patience! 😊

Could you help us troubleshoot by sending us your log files?

If you're still experiencing this issue please:

  • Take all of the log files under:
    C:\windows\logs\cbs\
    And the file: C:\Windows\Servicing\sessions\sessions.xml
  • Place them into a zip
  • And send them to my email: [email protected]

So no solution still? Seriously, issue was reported back in March.

You recommended DISM command but I'm running newly installed Windows. I will try running the command anyway.

EDIT: Tried. It finished in no time.

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.557

No component store corruption detected.
The operation completed successfully.

EDIT2: Feature update to Windows 10, version 1903 resolved the problem. 😃

Microsoft is actively investigating the issue. They have been working with me for the last two weeks to find a fix. Once they have a working fix, I'm sure it will be announced here.

IMHO: It seems to be a corrupted patch caused possibly by a subsequent patch. If you can't wait, you might try doing a fresh install of Windows 10 with NO patches and once the Linux sub system is installed then do your patching.

Hope this helps...

Update: Microsoft was able to resolve my issues. I'm sure they will post the instructions soon.

Where they will post how to solve this issue ?

@mscraigloewen any idea how soon you will have the official how-to available?

I've managed to solve the issue by upgrading to the latest Windows 10 version (which is, at this point, 18362.175).

Once we develop a general solution we'll post it here in this thread. This issue is happening because the optional component has gotten into a bad state. This can happen for a variety of reasons, and so the troubleshooting can often be specific, and therefore hard to generalize. We're working on getting a generalized solution!

Any updates on this issue?

We're still working on getting a generalized solution. Thank you for your patience, I know dealing with an error like this can be frustrating but we are still working on it, and I'll post any updates on the issue to this thread.

I am still getting the same issue

I was having this issue until I installed Windows version 1903 (I previously had version 1803). I had to go download it manually since my computer didn't find the most recent updates when I searched from my computer settings for some reason.

I had the same problem but worked around using the control panel.
Open Control Panel -> Programs and Features -> *Turn Windows Feature on or off * -> Check Windows Subsystem for Linux

2019/9/22
still have the same issue
maybe we should just use git bash for a moment

Same issue, can't add or remove anything on the Windows feature list.

As an update for this issue: We've been communicating with the team that owns the parts for the optional component install experience and they're aware of this issue and are investigating ways for a general fix.

In the meantime, I've added a reference to this issue into troubleshooting.md and compiled some of the solutions that people mentioned on this thread!

Here's the solution list so far:

  • If you are running the enable WSL feature command from PowerShell, try using the GUI instead by opening the start menu, searching for 'Turn Windows features on or off' and then in the list select 'Windows Subsystem for Linux' which will install the optional component.
  • Update your version of Windows by going to Settings, Updates, and clicking 'Check for Updates'
  • If both of those fail and you need to access WSL please consider upgrading in place by reinstalling Windows 10 using installation media and selecting 'Keep Everything' to ensure your apps and files are preserved. You can find instructions on how to do so at the Reinstall Windows 10 page.

Is there any update on a fix for this? This is blocking WSL usage at my company as the standard installation hits the bug :(

@cheshrkat I ended up fixing the issue by updating my Windows 10 image, I was several updates behind. I was a bit nervous going in, but nothing changed, I did not lose any files, and my WSL system worked perfectly afterwards.

@KirkBoyd unfortunately upgrading to the latest version is not an option in a controlled-installation corporate environment. Our machines are run on older feature builds with security patches applied - pretty common strategy, but one that really messes with WSL.

I request everyone to try running it in Administrative mode. That worked for me.

I seem to have the same exact issue and looking at this, it appears, this is still not fixed.

Having a similar issue as well...

This issue persists...
Windows 10 enterprise
Version 1809
Build 17763.1158
Capture

I still have this issue too

Still have this issue.
Running as administrator did not help.

Update: updating to 1909 fixed the issue for me.

I think Microsoft has really dropped the ball on this. I'll give them a day or two to respond and then post what I did to fix this issue with Microsofts help. Official Disclaimer: I don't work for Microsoft and don't warranty or guarantee any of information I share as correct for any given case or that it won't breaks something in the process.

I still have the issue

I think Microsoft has really dropped the ball on this. I'll give them a day or two to respond and then post what I did to fix this issue with Microsofts help. Official Disclaimer: I don't work for Microsoft and don't warranty or guarantee any of information I share as correct for any given case or that it won't breaks something in the process.

Please do so, we are several people affected by the issue. Thank you.

As an update for this issue: We've been communicating with the team that owns the parts for the optional component install experience and they're aware of this issue and are investigating ways for a general fix.

In the meantime, I've added a reference to this issue into troubleshooting.md and compiled some of the solutions that people mentioned on this thread!

Here's the solution list so far:

  • If you are running the enable WSL feature command from PowerShell, try using the GUI instead by opening the start menu, searching for 'Turn Windows features on or off' and then in the list select 'Windows Subsystem for Linux' which will install the optional component.
  • Update your version of Windows by going to Settings, Updates, and clicking 'Check for Updates'
  • If both of those fail and you need to access WSL please consider upgrading in place by reinstalling Windows 10 using installation media and selecting 'Keep Everything' to ensure your apps and files are preserved. You can find instructions on how to do so at the Reinstall Windows 10 page.

1st option does not work, and both 2nd and 3rd options are not possible on this company-owned laptop. I would be very interested in knowing the root cause and fixing that, not just using windows update / windows reinstall to regenerate broken files in order to fix it.

BEFORE YOU PROCEED:

The following is an email chain for fixing the issue I had with installing the linux subsystem on my company's Windows 10. It is in reverse chronological order. It may or may not be the same issue and/or solution you need. YOU are responsible for any damage it causes to your system, so be sure you know what you are doing before running a command. Also read through the ENTIRE conversation before proceeding. THERE ARE a few emails that I don't have anymore so they are is missing steps, I tried to note where they were.

Lastly, I have done my best to remove contact info so the guys that helped me don't get carpet bombed with email. If I missed something, be respectful.

- MJD

From: "User" <>
Date: Tuesday, June 18, 2019 at 2:29 PM
To: Troy S. <>, Ben H. <>, Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Kali Linux installed fine.

Thank you again for all your help guys!! You might want to share your fix instructions in the forum!

  • User

From: Troy S. <>
Date: Monday, June 17, 2019 at 9:12 PM
To: "User" <>, Ben H. <>, Craig L. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

That is good news.

Sent from my Windows 10 device

From: "User" <>
Sent: Monday, June 17, 2019 5:45:31 PM
To: Troy S.; Ben H.; Craig L.
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

I think that fixed it. I need to find the instructions to install a distro now to be sure.

THANK YOU!


Adding C:\KB4343909\expanded\x86_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_10.0.17134.112_none_3cf6dbcd428bcf88\osprovider.dll to Extraction Queue

Expanding Files ....
Progress: 26140 out of 26205 files
Expanding Files Complete ...
26205 files total.

C:\KB4343909>Dism /online /cleanup-image /restorehealth /source=c:\KB4343909\Expanded

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\KB4343909>Dism /online /remove-package /packagename=Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.228.1.6

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

Processing 1 of 1 - Removing package Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.228.1.6
[==========================100.0%==========================]
The operation completed successfully.

C:\KB4343909> Dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[=========== 20.0% ]
The operation completed successfully.

C:\KB4343909>
C:\KB4343909>

Ran the Powershell command and instead of erroring it asked me if I wanted to allow it to reboot.
I said, “Yes”
It rebooted
Now when I check Windows Features I show Windows Subsystem for Linux as installed.

  • User

From: Troy S. <>
Date: Monday, June 17, 2019 at 1:35 PM
To: "User" <>, Ben H. <>, Craig L. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

/Startcomponentcleanup isn’t accomplishing what I had hoped. Instead, use dism /remove-package (see step 13 below) to specifically remove the bad package.

Here’s the revised complete set of steps that are needed Note that steps 7-11 involve getting a new copy of the bad packaged downloaded and expanded so that it can be used by dism /restorehealth (step 12), and instead of immediately jumping to /startcomponentcleanup (step 14), try removing the bad package (step 13).

  1. From regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
  2. Give Administrators Full Control (you might have to click the Advanced button, and select Owner: Change, and add Administrators as the owner first) of the Packages key
  3. From regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0
  4. Give Administrators Full Control (you might have to click the Advanced button, and select Owner: Change, and add Administrators as the owner first) of the Packages key
  5. From regedit, Import the attached repair.txt file – this adds back the top level package that is missing
  6. Restore Administrators back to Read only permission for the above two keys
  7. Download https://www.catalog.update.microsoft.com/Search.aspx?q=KB4343909 (2018-08 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4343909)) Not the Delta package!!!
  8. Md c:\KB4343909
  9. Expand /f:* Windows10.0-KB4343909-x64.msu c:\KB4343909
  10. Md c:\KB4343909\Expanded
  11. Expand /f:* KB4343909\Windows10.0-KB4343909-x64.cab c:\KB4343909\Expanded
  12. Dism /online /cleanup-image /restorehealth /source=c:\KB4343909\Expanded
  13. Dism /online /remove-package /packagename=Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.228.1.6
  14. Dism /online /cleanup-image /startcomponentcleanup
  15. Reattempt the install of the WSL
  16. Send me the contents of c:\windows\logs\cbs if it fails again

From: "User" <>
Sent: Monday, June 17, 2019 11:16 AM
To: Troy S. <>; Ben H. <>; Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Ok, tried it a couple of times. Added additional key deletes and queries, but getting the same result each time.

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
MaintenanceFlags REG_DWORD 0x80010017

C:\WINDOWS\system32>reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags /f
The operation completed successfully.

C:\WINDOWS\system32>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags

ERROR: The system was unable to find the specified registry key or value.

C:\WINDOWS\system32>dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[=========== 20.0% ]
The operation completed successfully.

C:\WINDOWS\system32>reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
MaintenanceFlags REG_DWORD 0x80010017

C:\WINDOWS\system32>reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags /f
The operation completed successfully.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : The referenced assembly could not be found.
At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
  • ~~~~~~~~~~~~~~~~~

    • CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException

    • FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

  • User

From: Troy S. <>
Date: Friday, June 14, 2019 at 5:05 PM
To: "User" <>, Ben H. <>, Craig L. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

You forgot to delete MaintenanceFlags before running /startcomponentcleanup, so it didn’t do anything (it thinks nothing has changed since the last time it ran.)

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags /f
dism /online /cleanup-image /startcomponentcleanup

From: "User" <>
Sent: Friday, June 14, 2019 2:14 PM
To: Troy S. <>; Ben H. <>; Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> cd \temp
PS C:\temp> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : The referenced assembly could not be found.
At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
  • ~~~~~~~~~~~~~~~~~

    • CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException

    • FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

PS C:\temp>

  • User

From: Troy S. <>
Date: Friday, June 14, 2019 at 4:01 PM
To: "User" <>, Ben H. <>, Craig L. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Try installed WSL again and if it still fails send c:\windows\logs\cbs contents again.

Sent from my Windows 10 device

From: "User" <>
Sent: Friday, June 14, 2019 1:34:38 PM
To: Troy S.; Ben H.; Craig L.
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[=========== 20.0% ]
The operation completed successfully.

C:\WINDOWS\system32>

  • User

From: Troy S. <>
Date: Friday, June 14, 2019 at 3:24 PM
To: "User" <>, Ben H. <>, Craig L. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Yes, that is correct.

Sent from my Windows 10 device

From: "User" <>
Sent: Friday, June 14, 2019 1:01:38 PM
To: Troy S.; Ben H.; Craig L.
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Got it now, missed the Change owner on the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex

So next step is?
dism /online /cleanup-image /startcomponentcleanup

  • User

From: Troy S. <>
Date: Friday, June 14, 2019 at 2:12 PM
To: "User" <>, Ben H. <>, Craig L. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Did you do all of these steps?

  1. From regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
  2. Give Administrators Full Control (you might have to click the Advanced button, and select Owner: Change, and add Administrators as the owner first) of the Packages key
  3. From regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0
  4. Give Administrators Full Control (you might have to click the Advanced button, and select Owner: Change, and add Administrators as the owner first) of the Packages key
  5. From regedit, Import the attached repair.txt file – this adds back the top level package that is missing

You have to give Administrators full control of both registry keys listed above. Then import the repair.txt file.

From: "User" <>
Sent: Friday, June 14, 2019 11:44 AM
To: Troy S. <>; Ben H. <>; Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Troy,

I added Full Control to Administrator on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex andOwder is Administrator.

When I try to import the reg file I or add the key manually I get the same errors. So I tried to add Full Control to Administrator on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0
and I get Access Denied.

Thoughts?

  • User

From: Troy S. <>
Date: Friday, June 14, 2019 at 12:45 PM
To: "User" <>, Ben H. <>, Craig L. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

You will need to give Administrators Full Control (you might have to click the Advanced button, and select Owner: Change, and add Administrators as the owner before you can edit the Administrators access rights) of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0 key

That is what I meant by “You will need to give admin write access to this key, in addition to the Packages key mentioned previously. “

From: "User" <>
Sent: Friday, June 14, 2019 9:14 AM
To: Troy S. <>; Ben H. <>; Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Tried to do it manually with regedit running As Admin and got Cannot create value: Error writing to the registry.

  • User

From: "User" <>
Date: Friday, June 14, 2019 at 11:11 AM
To: Troy S. <>, Ben H. <>, Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

I’m running Regedit As Administrator and get this.

  • User

From: Troy S. <>
Date: Thursday, June 13, 2019 at 6:23 PM
To: "User" <>, Ben H. <>, Craig L. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

I missed one key that needs to be modified with the repair.txt file.

You will need to give admin write access to this key, in addition to the Packages key mentioned previously.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0

Then you can import this repair.txt file. After that dism /online /cleanup-image /startcomponentcleanup should be able to remove the bad package.

From: "User" <>
Sent: Thursday, June 13, 2019 12:44 PM
To: Troy S. <>; Ben H. <>; Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

reg save "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" cbs.hiv

From: Troy S. <>
Date: Wednesday, June 12, 2019 at 6:04 PM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

That made progress. Can you do a reg save to get the cbs.hiv again please?

From: "User" <>
Sent: Wednesday, June 12, 2019 3:55 PM
To: Troy S. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

I re-ran all the step with your modifications

...
...
...
Adding C:\Temp\kb4343909-x64\expended\x86_dual_ntprint.inf_31bf3856ad364e35_10.0.17134.191_none_6a6f5435e7754b67\i386\p6font.gpd to Extraction Queue
Adding C:\Temp\kb4343909-x64\expended\amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17134.191_none_c68defb99fd2bc9d\amd64\p6font.gpd to Extraction Queue
Adding C:\Temp\kb4343909-x64\expended\x86_dual_ntprint.inf_31bf3856ad364e35_10.0.17134.191_none_6a6f5435e7754b67\i386\p6disp.gpd to Extraction Queue
Adding C:\Temp\kb4343909-x64\expended\amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17134.191_none_c68defb99fd2bc9d\amd64\p6disp.gpd to Extraction Queue
Adding C:\Temp\kb4343909-x64\expended\x86_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_10.0.17134.112_none_3cf6dbcd428bcf88\osprovider.dll to Extraction Queue

Expanding Files ....
Progress: 26081 out of 26205 files
Expanding Files Complete ...
26205 files total.

C:\Temp\kb4343909-x64>reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing /v LocalSourcePath /t REG_SZ /d C:\Temp\kb4343909-x64\expended
Value LocalSourcePath exists, overwrite(Yes/No)? yes
The operation completed successfully.

C:\Temp\kb4343909-x64>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Temp\kb4343909-x64>reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing /v LocalSourcePath /f
The operation completed successfully.

C:\Temp\kb4343909-x64>reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags /f

C:\Temp\kb4343909-x64>dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[===========================99.0%========================= ]
[=========== 20.0% ]
The operation completed successfully.

PS C:\temp> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : The referenced assembly could not be found.
At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
  • ~~~~~~~~~~~~~~~~~

    • CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException

    • FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

From: Troy S. <>
Date: Wednesday, June 12, 2019 at 5:11 PM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags /f
dism /online /cleanup-image /startcomponentcleanup


<< 1 or 2 emails lost here, but not likely relavant >>>


Sorry, I gave you the wrong format type for the localsource registry value. It is supposed to be REG_SZ, not REG_MULTI_SZ, so /restorehealth was unable to use the local source to repair the store.

reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing /v LocalSourcePath /t REG_SZ /d C:\Temp\kb4343909-x64\expanded

From: User <>
Sent: Wednesday, June 12, 2019 2:53 PM
To: Troy S. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Sorry, didn’t realize you wanted that.

  • User

From: Troy S. <>
Date: Wednesday, June 12, 2019 at 4:46 PM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

I need to see the cbs.log. The dism.log isn’t all that useful for online operations.

From: User <>
Sent: Wednesday, June 12, 2019 2:42 PM
To: Troy S. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Results…

C:\WINDOWS\system32>cd \temp

C:\Temp>reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing /v LocalSourcePath /t REG_MULTI_SZ /d C:\Temp\kb4343909-x64\expanded
The operation completed successfully.

C:\Temp>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[===========================84.4%================ ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\Temp>

  • User

From: Troy S. <>
Date: Wednesday, June 12, 2019 at 3:51 PM
To: "User" <>, Craig L. <>
Cc: Ben H. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

It is still unable to remove the bad package, because of the missing files, but at least it sees the top level package now. Here’s what you can do:

If you still have the Windows10.0-KB4343909-x64.cab available (from the expansion of the .msu), expand it to a local directory. Then add it as a local source for corruption repair and run restorehealth again like:

md c:\temp\KB4343909-x64\expanded
expand /f:* C:\Temp\kb4343909-x64\Windows10.0-KB4343909-x64.cab c:\temp\KB4343909-x64\expanded
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing /v LocalSourcePath /t REG_MULTI_SZ /d c:\temp\KB4343909-x64\expanded

dism /online /cleanup-image /restorehealth

If that completes and repairs all corruptions then you can remove the local source path from the registry like:

reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing /v LocalSourcePath /f

At that point try running dism /cleanup-image /startcomponentcleanup again

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags /f
dism /online /cleanup-image /startcomponentcleanup

From: User <>
Sent: Wednesday, June 12, 2019 12:52 PM
To: Troy S. <>; Craig L. <>
Cc: Ben H. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

C:\Temp>reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags /f
The operation completed successfully.

C:\Temp>dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[=========== 20.0% ]
The operation completed successfully.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : The referenced assembly could not be found.
At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
  • ~~~~~~~~~~~~~~~~~

    • CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException

    • FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

PS C:\WINDOWS\system32>

From: Troy S. <>
Date: Wednesday, June 12, 2019 at 2:45 PM
To: "User" <>, Craig L. <>
Cc: Ben H. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Re-attaching the repair file, since it was detected as malware.

From: Troy S.
Sent: Wednesday, June 12, 2019 12:41 PM
To: 'User' <>; Craig L. <>
Cc: Ben H. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

One other thing, before step 5, run the following from an elevated CMD prompt. It will ensure that /startcomponentcleanup does a full set of processing, rather than skipping already completed tasks.

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v MaintenanceFlags /f

From: Troy S.
Sent: Wednesday, June 12, 2019 12:26 PM
To: User <>; Craig L. <>
Cc: Ben H. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

FYI, there shouldn’t be any PII (privacy related information) in the cbs.hiv, or c:\windows\logs\cbs

You package store is corrupt. The top level package for KB4343909 (Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.228.1.6) is missing, yet the child packages are still listed as remaining. However, it appears that two of the child packages’ files are no longer in the store. I think you can repair this by:

From regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
Give Administrators Full Control (you might have to click the Advanced button, and select Owner: Change, and add Administrators as the owner first) of the Packages key
Import the attached repair.reg.txt file – this adds back the top level package that is missing
Restore Administrators back to Read only permission
From elevated CMD prompt run: dism /online /cleanup-image /startcomponentcleanup
Send me the c:\windows\logs\cbs\cbs.log after the cleanup
You can try installing WSL again at this point

From: User <>
Sent: Wednesday, June 12, 2019 11:37 AM
To: Craig L. <>; Troy S. <>
Cc: Ben H. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Info and files you requested. For security reasons the zip file is password protected. Password will come in a different message.

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd \temp

C:\Temp>Dir /b c:\windows\servicing\packages*KB4343909*.mum
Package_1000_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1001_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1002_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1004_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1005_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1006_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1007_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1008_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1009_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1010_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1011_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1012_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1013_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1014_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1015_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1016_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1019_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1020_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1021_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1022_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1023_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1024_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1026_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1027_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1028_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1029_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1030_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1031_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1032_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1033_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1034_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1035_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1036_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1037_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1038_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1039_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1040_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1041_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1042_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1043_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1044_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1045_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1046_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1047_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1048_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1049_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1050_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1051_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1052_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1053_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1054_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1055_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1056_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1057_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1058_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1059_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1060_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1061_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1062_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1063_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1064_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1065_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1066_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1067_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1068_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1069_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1071_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1073_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1075_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1077_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1079_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1081_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1083_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1084_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1085_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1087_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1089_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1091_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1093_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1095_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1097_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1099_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1101_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1103_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1105_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1107_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1109_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1111_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1113_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1115_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1116_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1117_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1119_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1121_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1123_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1125_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1127_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1129_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1131_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1133_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1135_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1137_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1139_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1141_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1143_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1145_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1147_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1148_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1149_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1150_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1151_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1152_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1153_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1154_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1155_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1156_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1157_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1158_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1159_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1160_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1161_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1162_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1163_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1164_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1165_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1166_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1167_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1168_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1169_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1170_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1171_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1172_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1173_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1174_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1175_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1177_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1184_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1202_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1203_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1204_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1205_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1206_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1207_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1223_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1224_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1225_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1226_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1227_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1228_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1229_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1230_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1231_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1232_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1233_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1234_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1235_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1236_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1237_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1238_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1239_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1240_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1241_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1242_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1243_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1244_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1245_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1246_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1247_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1248_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1249_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1250_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1251_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1252_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1253_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1254_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1255_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1256_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1257_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1258_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1259_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1260_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1261_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1262_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1263_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1264_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1265_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1266_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1267_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1268_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1269_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1270_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1271_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1272_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1273_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1274_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1275_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1276_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1277_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1278_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1279_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1280_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1281_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1282_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1283_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1284_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1285_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1286_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1287_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1288_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1289_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1290_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1291_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1292_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1293_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1294_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1295_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1296_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1297_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1298_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1299_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1300_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1301_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1302_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1303_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1304_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1305_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1306_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1307_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1308_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1309_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1346_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1380_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1394_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1410_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1411_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1430_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1431_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1432_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1433_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1434_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1448_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1449_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1463_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1464_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1465_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1466_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1467_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1468_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1469_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1470_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1471_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1472_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1473_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1474_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1475_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1488_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1489_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1490_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1491_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1492_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1493_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1494_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1495_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1496_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1497_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1498_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1499_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1500_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1507_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1508_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1509_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1510_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1511_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1512_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1513_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1514_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1515_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1516_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1517_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1525_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1541_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1542_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1543_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1559_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1560_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1561_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1562_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1563_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1564_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1565_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1566_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1567_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1568_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1569_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1570_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1571_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1584_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1585_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1586_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1587_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1588_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1589_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1590_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1591_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1602_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1603_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1617_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1618_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1654_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1655_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1656_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1657_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1658_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1659_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1694_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1695_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1696_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1697_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1699_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1701_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1703_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1705_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1707_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1708_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1709_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1710_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1713_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1714_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1715_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1716_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1717_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1719_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1721_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1723_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1725_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1726_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1727_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1729_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1730_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1731_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1732_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1733_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1734_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1735_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1736_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1737_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1738_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1739_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1741_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1743_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1745_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1747_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1748_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1750_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1751_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1752_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1753_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1755_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1756_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1758_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1759_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1761_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1763_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1764_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1765_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1766_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1767_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1768_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1769_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1770_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1771_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1772_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1773_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1774_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1775_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1776_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1777_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1778_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1779_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1780_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1781_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1782_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1783_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1784_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1785_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1786_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1787_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1788_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1789_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1790_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1791_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1792_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1793_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1801_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1817_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1818_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1819_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1835_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1836_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1837_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1838_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1839_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1840_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1844_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1845_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1846_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1847_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1850_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_1851_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_1975_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2011_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2012_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2013_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2026_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2051_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2052_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2151_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2152_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2153_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2154_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2155_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2165_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2170_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2171_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2213_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2214_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2222_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2238_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2239_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2255_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2263_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2279_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2280_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2297_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2298_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2299_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2300_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2301_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2302_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2303_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2304_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2306_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2307_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2308_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2309_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2310_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2312_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2326_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2336_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2339_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2340_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2341_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2342_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2366_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2367_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2368_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2369_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2371_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2376_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2377_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2378_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2379_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2382_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2383_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2384_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2385_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2386_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2387_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2388_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2389_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2390_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2391_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2394_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2397_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2398_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2399_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2400_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2401_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2422_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2423_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2424_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2425_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2427_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2428_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2429_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2431_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2432_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2433_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2434_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2435_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2436_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2444_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2445_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2446_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2447_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2448_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2449_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2453_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2454_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2455_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2456_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2457_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2458_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2459_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2460_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2461_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2465_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2466_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_2469_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_2470_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_755_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_756_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_757_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_759_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_760_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_761_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_762_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_763_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_764_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_765_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_766_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_767_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_768_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_769_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_770_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_771_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_784_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_785_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_795_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_796_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_797_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_798_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_799_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_800_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_801_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_802_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_803_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_804_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_805_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_806_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_807_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_808_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_809_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_810_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_811_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_812_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_813_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_814_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_815_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_816_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_817_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_818_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_819_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_820_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_821_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_822_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_823_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_824_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_825_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_826_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_827_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_828_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_829_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_831_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_832_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_840_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_856_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_872_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_873_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_874_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_875_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_876_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_877_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_879_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_880_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_881_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_882_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_883_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_884_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_885_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_886_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_887_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_888_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_889_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_890_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_891_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_892_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_893_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_894_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_902_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_918_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_919_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_935_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_936_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_937_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_938_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_939_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_962_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_978_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_979_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_980_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_981_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_982_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_983_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_984_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_985_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_986_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_987_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_988_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_989_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_990_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_991_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_992_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_993_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_994_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_995_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_996_for_KB4343909~31bf3856ad364e35~amd6410.0.1.6.mum
Package_997_for_KB4343909~31bf3856ad364e35~amd64
10.0.1.6.mum
Package_998_for_KB4343909~31bf3856ad364e35~amd64~~10.0.1.6.mum

C:\Temp>

  • User

From: Craig L. <>
Date: Wednesday, June 12, 2019 at 11:57 AM
To: "User" <>, Troy S. <>
Cc: Ben H. <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Hi Michael,

I’m adding Troy S. who is helping us debug this in our end, and Ben H. a dev on WSL.

Could you run this command and send us cbs.hiv

reg save "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing" cbs.hiv

Also, can I get copies of the contents of c:\windows\logs\cbs again?

Thanks,
-Craig

From: User <>
Sent: Tuesday, June 11, 2019 5:15 PM
To: Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Np, thank you for the help!!

  • User

From: Craig L. <>
Date: Tuesday, June 11, 2019 at 7:12 PM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Dang! Thanks for your patience on this, we’ll keep digging!

From: User <>
Sent: Tuesday, June 11, 2019 5:12 PM
To: Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Yes, same error

From: Craig L. <>
Date: Tuesday, June 11, 2019 at 7:08 PM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

And now if you enable WSL? Still the same error?

From: User <>
Sent: Tuesday, June 11, 2019 5:07 PM
To: Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> Dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

[=========== 20.0% ]
The operation completed successfully.
PS C:\WINDOWS\system32>

  • User

From: Craig L. <>
Date: Tuesday, June 11, 2019 at 6:38 PM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Could you try this command in Powershell and then try installing the component?

Dism /online /cleanup-image /startcomponentcleanup

From: User <>
Sent: Tuesday, June 11, 2019 12:21 PM
To: Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Not there yet, but I see what you are trying to do. Here is the log or what I tried.

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd \temp

C:\Temp>dir
Volume in drive C has no label.
Volume Serial Number is FABE-896C

Directory of C:\Temp

06/11/2019 11:20 AM

.
06/11/2019 11:20 AM ..
06/10/2019 04:15 PM 423,020,048 windows10.0-kb4343909-x64_delta_2d46c39ffab8b34e9d47c63384571ba53566af41.msu
06/10/2019 04:11 PM 770,518,268 windows10.0-kb4343909-x64_f931af6d56797388715fe3b0d97569af7aebdae6.msu
2 File(s) 1,193,538,316 bytes
2 Dir(s) 12,751,970,304 bytes free

C:\Temp>mkdir kb4343909-x64

C:\Temp>expand /f:* windows10.0-kb4343909-x64_f931af6d56797388715fe3b0d97569af7aebdae6.msu kb4343909-x64
Microsoft (R) File Expansion Utility
Copyright (c) Microsoft Corporation. All rights reserved.

Adding kb4343909-x64\WSUSSCAN.cab to Extraction Queue
Adding kb4343909-x64\Windows10.0-KB4343909-x64.cab to Extraction Queue
Adding kb4343909-x64\Windows10.0-KB4343909-x64-pkgProperties.txt to Extraction Queue
Adding kb4343909-x64\Windows10.0-KB4343909-x64.xml to Extraction Queue

Expanding Files ....
Progress: 1 out of 4 files
Expanding Files Complete ...
4 files total.

C:\Temp>Dism /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~17134.228.1.6

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

An error occurred trying to open - Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~17134.228.1.6 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\Temp>dism /online /add-package /packagepath=C:\Temp\kb4343909-x64\Windows10.0-KB4343909-x64.cab

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.228.1.6
[==========================100.0%==========================]
The operation completed successfully.

So since this second command was successful, I went over to powershell and tried install again.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : The referenced assembly could not be found.
At line:1 char:2

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows ...
  • ~~~~~~~~~~~~~~~~

    • CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException

    • FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

PS C:\WINDOWS\system32>

Then I went back to command prompt and tried the remove-package again.

C:\Temp>Dism /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~17134.228.1.6

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

An error occurred trying to open - Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~17134.228.1.6 Error: 0x800f0805
The specified package is not valid Windows package.

Error: 0x800f0805

The specified package is not valid Windows package.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\Temp>

From: Craig L. <>
Date: Tuesday, June 11, 2019 at 11:37 AM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Here’s some more follow up!

Tell them not to use the delta packages, because they are not full packages, and it is just asking for trouble to mix full packages and delta packages. They should first make sure that the delta package has been removed by:

Dism /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~17134.228.1.6

Then use the following command line to install the KB.

dism /online /add-package /packagepath=C:\Temp\kb4343909-x64\Windows10.0-KB4343909-x64.cab

From: User <>
Sent: Monday, June 10, 2019 4:17 PM
To: Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

I tried it a few different ways, from C:\Temp and from inside the directory. It errored each time. Including the log file…

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd \temp

C:\Temp>dir
Volume in drive C has no label.
Volume Serial Number is FABE-896C

Directory of C:\Temp

06/10/2019 06:09 PM

.
06/10/2019 06:09 PM ..
06/10/2019 06:05 PM kb4343909-x64
06/10/2019 06:10 PM kb4343909-x64-delta
06/10/2019 04:15 PM 423,020,048 windows10.0-kb4343909-x64_delta_2d46c39ffab8b34e9d47c63384571ba53566af41.msu
06/10/2019 04:11 PM 770,518,268 windows10.0-kb4343909-x64_f931af6d56797388715fe3b0d97569af7aebdae6.msu
2 File(s) 1,193,538,316 bytes
4 Dir(s) 11,206,406,144 bytes free

C:\Temp>dism /online /add-package /packagepath=C:\Temp\kb4343909-x64-delta

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

An error occurred trying to open - WSUSSCAN.cab Error: 0x80070002
Processing 1 of 1 - Adding package Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~17134.228.1.6
[==========================100.0%==========================]

Error: 2

The specified package is not applicable to this image.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\Temp>dism /online /add-package /packagepath=C:\Temp\kb4343909-x64

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.765

An error occurred trying to open - WSUSSCAN.cab Error: 0x80070002
Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~17134.228.1.6
[==========================100.0%==========================]

Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\Temp>dir kb4343909-x64
Volume in drive C has no label.
Volume Serial Number is FABE-896C

Directory of C:\Temp\kb4343909-x64

06/10/2019 06:05 PM

.
06/10/2019 06:05 PM ..
08/03/2018 06:30 PM 517 Windows10.0-KB4343909-x64-pkgProperties.txt
08/03/2018 06:29 PM 771,219,439 Windows10.0-KB4343909-x64.cab
08/03/2018 06:30 PM 453 Windows10.0-KB4343909-x64.xml
08/03/2018 06:34 PM 449,564 WSUSSCAN.cab
4 File(s) 771,669,973 bytes
2 Dir(s) 11,205,644,288 bytes free

C:\Temp>dir kb4343909-x64-delta
Volume in drive C has no label.
Volume Serial Number is FABE-896C

Directory of C:\Temp\kb4343909-x64-delta

06/10/2019 06:10 PM

.
06/10/2019 06:10 PM ..
08/03/2018 08:09 PM 515 Windows10.0-KB4343909-x64-pkgProperties_Delta.txt
08/03/2018 08:07 PM 423,173,648 Windows10.0-KB4343909-x64_Delta.cab
08/03/2018 08:09 PM 467 Windows10.0-KB4343909-x64_Delta.xml
08/03/2018 08:13 PM 455,750 WSUSSCAN.cab
4 File(s) 423,630,380 bytes
2 Dir(s) 11,205,632,000 bytes free

C:\Temp>

  • User

From: Craig L. <>
Date: Monday, June 10, 2019 at 5:12 PM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

Notice: This email is from an external sender.

Could you try extracting the contents of the .msu and use dism to perform the install. That would look something like this:

Md KB4343909
expand /f:* Windows10.0-KB4343909-x64.msu KB4343909
dism /online /add-package /packagepath=KB4343909

From: User <>
Sent: Monday, June 10, 2019 2:20 PM
To: Craig L. <>
Subject: Re: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

I downloaded and attempted to install 2018-08 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4343909) and it said, “The update is not applicable to your computer.”
So I downloaded and attempted to install 2018-08 Delta Update for Windows 10 Version 1803 for x64-based Systems (KB4343909). It started to extract the update and then it said, “The update is not applicable to your computer.”.

  • User

From: Craig L. <>
Date: Monday, June 10, 2019 at 4:05 PM
To: "User" <>
Subject: RE: [MicrosoftDocs/WSL] Error - The referenced assembly could not be found (#368)

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4343909

Was this page helpful?
0 / 5 - 0 ratings