Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by abbodi1406

  1. With the July mess on .NET updates, i decided to wait until next Tuesday to see if they release new Preview Rollup otherwise, i will update addon with KB4344146
  2. I only found 4.6.1 https://sendit.cloud/fqnenfjsi8iy https://sendit.cloud/vc1sx4fcisxf
  3. @Pavel Addon is already 4.7.3130.4 -- I don't have time to rebuild addon with KB4346407 fix (4.7.3133.2), and new rollup will be released in two weeks anyway here's temporary updated .net 4.7.2 setup, based of @ricktendo installer http://www.mediafire.com/file/3rs355nt4d1wfwo File: dotNetFx472_Slim_x86_x64.exe SHA-1: 2047568b2e36977d699afcbcdc398d06cf488e44 SHA-256: 50a0a9c1d768d060d4c787f99e9d95e4ac9b43ea3c75e3f00e725fab614ee935 File: dotNetFx472_Slim_x86_x64.zip SHA-1: d37d242db437651a4d28ff4aa0974f878bae6bc8 SHA-256: 446c05ced8f1c58f32c9cf5a109ae7547f4b95c37b6d8953f8923ab011c03712
  4. For Windows 7, you can get NDP472-KB4054541-x86-x64-ENU.exe + NDP472-KB4087364 from catalog http://www.catalog.update.microsoft.com/Search.aspx?q=KB4054530 it will be the same as new NDP472-KB4054530-x86-x64-AllOS-ENU.exe because this one include KB4087364 patch
  5. No .NET 4.x is part of Win 8.1 and updated with regular updates https://download.microsoft.com/download/b/9/5/b95136c0-58a0-48df-821a-d05319a86852/enu_NETFX/amd64_windows8_1-kb4054566-x86_cab/windows8.1-kb4054566-x86.cab https://download.microsoft.com/download/b/9/5/b95136c0-58a0-48df-821a-d05319a86852/enu_NETFX/amd64_windows8_1-kb4054566-x64_cab/windows8.1-kb4054566-x64.cab
  6. I see did you installed KB4099950? anyway, WU have became more messy in 2018 with QualityCompat and PCIClearStaleCache.exe
  7. Does it have QualityCompat registry key? because it's still needed by WU to complete the supersedence chain for rollups
  8. Updated hopefully they don't change the release version tomorrow
  9. KB4099950 contain PCIClearStaleCache.exe which can be executed on live OS only it checks pci.sys version and clear the registry cache for NIC (if exist) if KB4088875 is integrated offline, the stale cache will not exist, and KB4099950 will just ran and installed without fixing anything
  10. It can be integrated, but it will not fix the issue (if present) just like KB3046269 and KB2603229 although in KB4099950 case, if latest rollup is integrated offline before installing the OS, the NIC issue will not occur
  11. Did you installed KB4019990 too? anyway, Win7 WU is mess, and will always offer old superseded updates
  12. Yes, you can add it manually easily, but only if you do not use Anti-Virus program otherwise it must be compatible and it should add the key
  13. There will be new update this Tuesday, will see what happens and i will make a note about the QualityCompat registry key requirement
  14. KB4076492 does not have new update, it still bundles KB4054981 i do not have this issue on en-us Windows 7 but i will check again and see, if so, i'll add KB4074880 one thing to check, do you have QualityCompat registry key set? all updates since January 2018 will not be recognized or detected by WU without it, including .NET rollup
  15. They must have changed something in WU detection because when i created the addon, i test it and WU did not offer any .NET 4 update did you installed KB4019990?
  16. Thanks for the SFXs there is a problem with KB4055002 for .NET 4.7.1, where it replace inbox 4.7.2558.0 files with 4.7.2117.0 files https://blogs.msdn.microsoft.com/dotnet/2018/01/09/net-framework-january-2018-security-and-quality-rollup/#comments i see you managed to exclude almost all the older files in your repack but you missed \v4.0.30319\WPF\Fonts\GlobalUserInterface.CompositeFont you need to restore the one from .NET 4.7.1 manually (dated 2017-07-12) also, there is a reliability companion .NET 4.7.1 update KB4054852 (it's not included or related to KB405500) it's ditributed with KB4033342 in catalog Regards.
  17. Latest .NET rollups do not replace *all*components in previous rollups meaning, each new rollup contain new components or new version of existing components + the components that did not change in CBS mechanism rules, the *shared* components makes previous rollup only partially superseded, thus not removed by DeepClean Windows Monthly Rollups have the same case, but these are linked together by CBS package name Package_for_RollupFix which makes previous rollups always superseded, regardless the components
  • Create New...