Jump to content

abbodi1406

Members
  • Content Count

    369
  • Joined

  • Last visited

  • Days Won

    92

Everything posted by abbodi1406

  1. I see did you installed KB4099950? anyway, WU have became more messy in 2018 with QualityCompat and PCIClearStaleCache.exe
  2. Does it have QualityCompat registry key? because it's still needed by WU to complete the supersedence chain for rollups
  3. Updated hopefully they don't change the release version tomorrow
  4. 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
  5. 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
  6. Did you installed KB4019990 too? anyway, Win7 WU is mess, and will always offer old superseded updates
  7. 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
  8. There will be new update this Tuesday, will see what happens and i will make a note about the QualityCompat registry key requirement
  9. 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
  10. 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?
  11. 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.
  12. 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
  13. Updated i'm aware of the issue in KB4055002, the addon have the correct files and the issue should not occur
  14. current Wintoolkit addon mechanism can't handle 2005/2008 https://www.wincert.net/forum/index.php?/topic/12624-obsolete-microsoft-visual-c-redistributable-packages/&do=findComment&comment=117558
  15. Added .NET 4.7.1 LangPacks Addons be sure to integrate them after main addon
  16. Why do you need them, if i may ask? those addons do not correctly handle MOFs and performance counters besides, all 4.6 or 4.6.1 or 4.6.2 versions get the same update targeted for 4.7, which basically transform your version to 4.7 inadvertently so it's better to have full 4.7 or the older 4.5.2 which is still separate
  17. Yes, but i got busy a little bit if they don't release new updatethis tuesday, i will update the addon with KB4043766
×
×
  • Create New...