Windows 10 Hotfix Repository

No, but i just did:

Code:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:f:\ToolKit-v8.8\Mount\Install\1\ /Add-Package /PackagePath:f:\ToolKit-v8.8\Packs\WHD\w10\x86\ServicingStack\

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.1

Processing 1 of 1 - Adding package Package_for_KB4465477~31bf3856ad364e35~x86~~17763.52.1.1
[==========================100.0%==========================]
The operation completed successfully.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:f:\ToolKit-v8.8\Mount\Install\1\ /Add-Package /PackagePath:f:\ToolKit-v8.8\Packs\WHD\w10\x86\FlashPlayer\

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.1

Processing 1 of 1 - Adding package Package_for_KB4462930~31bf3856ad364e35~x86~~10.0.1.0
[==========================100.0%==========================]
The operation completed successfully.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:f:\ToolKit-v8.8\Mount\Install\2\ /Add-Package /PackagePath:f:\ToolKit-v8.8\Packs\WHD\w10\x86\ServicingStack\

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.1

Processing 1 of 1 - Adding package Package_for_KB4465477~31bf3856ad364e35~x86~~17763.52.1.1
[==========================100.0%==========================]
The operation completed successfully.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:f:\ToolKit-v8.8\Mount\Install\2\ /Add-Package /PackagePath:f:\ToolKit-v8.8\Packs\WHD\w10\x86\FlashPlayer\

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.1

Processing 1 of 1 - Adding package Package_for_KB4462930~31bf3856ad364e35~x86~~10.0.1.0
[==========================100.0%==========================]
The operation completed successfully.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:f:\ToolKit-v8.8\Mount\Install\3\ /Add-Package /PackagePath:f:\ToolKit-v8.8\Packs\WHD\w10\x86\ServicingStack\

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.1

Processing 1 of 1 - Adding package Package_for_KB4465477~31bf3856ad364e35~x86~~17763.52.1.1
[==========================100.0%==========================]
The operation completed successfully.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:f:\ToolKit-v8.8\Mount\Install\3\ /Add-Package /PackagePath:f:\ToolKit-v8.8\Packs\WHD\w10\x86\FlashPlayer\

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.1

Processing 1 of 1 - Adding package Package_for_KB4462930~31bf3856ad364e35~x86~~10.0.1.0
[==========================100.0%==========================]

Error: 0x800f081e

The specified package is not applicable to this image.

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

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:f:\ToolKit-v8.8\Mount\Install\4\ /Add-Package /PackagePath:f:\ToolKit-v8.8\Packs\WHD\w10\x86\ServicingStack\

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.1

Processing 1 of 1 - Adding package Package_for_KB4465477~31bf3856ad364e35~x86~~17763.52.1.1
[==========================100.0%==========================]
The operation completed successfully.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>DISM /Image:f:\ToolKit-v8.8\Mount\Install\4\ /Add-Package /PackagePath:f:\ToolKit-v8.8\Packs\WHD\w10\x86\FlashPlayer\

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.1

Processing 1 of 1 - Adding package Package_for_KB4462930~31bf3856ad364e35~x86~~10.0.1.0
[==========================100.0%==========================]

Error: 0x800f081e

The specified package is not applicable to this image.

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

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>

Index 1 = Home
Index 2 = Home N
Index 3 = Enterprise 2019 LTSC (Not applicable)
Index 4 = Enterprise N 2019 LTSC (Not applicable)

 

Flash for 1809 applicability list:

Code:

<assemblyIdentity name="Microsoft-Windows-CoreCountrySpecificEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-CoreEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-CoreNEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseGEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseNEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ProfessionalNEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />

 

..The error with the integrations in OFLINE occurs only with the LTSC 2019....

 

Yep: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-329#post-1471380\
Reason: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-329#post-1471386
LTSC is not present in the list.

 

Is this intended? No Flash for LTSC?

 

It looks that way.

 

thanks,
ver 1809 is redstone 5 ? which is coming in nov-dec 2018 ?

 

@abbodi1406Good day, Seams W10UI_5.2 ignores this month Flash updates.
Could you take a look please?
Thanks as always.

 

You need to login to view this posts content.

 

hmm sometimes I wonder: why do people need to install and use MSRT?

 

Hi! Any chance about fixing the space issue with UUPDL? Thanks.

Screenshot:

 

What space issue ? Spaces in the path? Latter can only be fixed if all used sub-scripts would support it, it's not the CMD alone that needs to get them correctly .

 

I know, the problem is with 7zip, it can't find the right path, because it contains spaces. I will try to fix it.

 

Yes, PLS fight it...

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\MRT]
"DontOfferThroughWUAU"=dword:00000001

 

HI armond yep I know a long time but thanks anyway bro

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

very useful to fix a BSOD. thanks MS

 

That's what I also thougt. WTF, a non-servicable update to fix a problem that can occur right away?