Windows 10 Hotfix Repository

Discussion in 'Windows 10' started by Tito, Oct 1, 2014.

  1. Tiko

    Tiko MDL Junior Member

    Aug 18, 2014
    53
    4
    0
    Only I did not receive an update for LTSC2019 flash player kв4462930, or should it be ???
     
  2. Trenchboygun

    Trenchboygun MDL Member

    Apr 8, 2013
    158
    92
    10
    I dont use script, do it manually
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,273
    94,757
    450
    I can do it manually, but that wouldn't lead to a fix for @abbodi1406 his script, would it?
     
  4. Trenchboygun

    Trenchboygun MDL Member

    Apr 8, 2013
    158
    92
    10
  5. WhiteDeath1313

    WhiteDeath1313 MDL Member

    Aug 25, 2018
    124
    276
    10
    i hope the script will be updated from my friend said the msmg integrate the adobe update...but i did big aio and i notice last the script didnt integrate adobe but i skipped it as long the most important in this case (1809) is the CU.
     
  6. tavrez

    tavrez MDL Senior Member

    Sep 28, 2015
    484
    315
    10
    I got it, that's why I wrote "Also". :D
    I mentioned it because it is maybe the reason of it, something is wrong with package and script fails to integerate it. Did you tried manual integration as well?
    Edit: seems like you did, sorry didn't see it
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,273
    94,757
    450
    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)
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,273
    94,757
    450
    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" />
     
  9. kuroda

    kuroda MDL Senior Member

    Aug 25, 2012
    445
    32
    10
    ..The error with the integrations in OFLINE occurs only with the LTSC 2019....
     
  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,273
    94,757
    450
  11. tavrez

    tavrez MDL Senior Member

    Sep 28, 2015
    484
    315
    10
    Is this intended? No Flash for LTSC?
     
  12. s1ave77

    s1ave77 Has left at his own request

    Aug 15, 2012
    16,104
    24,378
    340
    It looks that way.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Ahsan

    Ahsan MDL Addicted

    Dec 3, 2009
    828
    167
    30
  14. armond

    armond MDL Addicted

    Jun 16, 2008
    734
    235
    30
    @abbodi1406Good day, Seams W10UI_5.2 ignores this month Flash updates.:(
    Could you take a look please?
    Thanks as always.
     
  15. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    7,897
    10,733
    240
    hmm sometimes I wonder: why do people need to install and use MSRT? :rolleyes:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Cobra91151

    Cobra91151 MDL Member

    Jun 17, 2011
    162
    46
    10
    Hi! Any chance about fixing the space issue with UUPDL? Thanks.

    Screenshot:
     

    Attached Files:

  17. s1ave77

    s1ave77 Has left at his own request

    Aug 15, 2012
    16,104
    24,378
    340
    What space issue :g:? 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 :cool2:.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. Cobra91151

    Cobra91151 MDL Member

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