Windows 10 Hotfix Repository

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?

 

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.

 

Code:

In
Windows10.0-KB4462930-x64-pkgProperties.txt

ApplicabilityInfo="Windows 10.0 Client;Windows 10.0 Server;"

and

In
update.mum

      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />

Could be add to Server?

 

I showed x86, server is x64 only, so the x64 version should contain server too, at least the server sku's containing flash.

x64:

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-EnterpriseSEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEvalEdition" 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" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      <assemblyIdentity name="Microsoft-Windows-ServerStandardEvalEdition" version="10.0.17763.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />

 

not have Windows\System32\Macromed folder(nonGUI and GUI), but in GUI version had some about flash files in Windows\servicing\Packages\, like Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~10.0.17763.1.cat and mum else.

i don't know about the status.

 

Back to overrated status

v5.2 will never integrate it to any edition, because it checks for Adobe-Flash-For-Windows-Package, which no longer exist in 17763
instead, Flash is now derived from Microsoft-Windows-Client-Desktop-Required-Package

 

Is this only happening in 1809?

 

Yes

but it seems Adobe-Flash-For-Windows-Package still exist in Server 2019 editions