Jump to content

abbodi1406

Members
  • Content Count

    360
  • Joined

  • Last visited

  • Days Won

    81

Everything posted by abbodi1406

  1. All .NET 4.6.x Rollups are cumulative, last one relace them all this applies to MSI version (Windows 7) Windows 8.1 MSU has a different behavior
  2. Name: dotNetFx_AIO_x86_20170412.exe Size: 68222035 bytes (65 MB) SHA1: 72E6800C3FE119D32380323C61CE84739CAF4FEF SHA256: 6A64C00E69FC846810ECE96A10E7AE7AA673852AF29A8FC040E44A3D69D32FAF http://sendit.cloud/k5eoou3bi8f3 http://www.mirrorcreator.com/files/0RCGOXPA/
  3. Sorry, i never experienced such issue, and the log does not list any related error i'll do a test install with updated image to see
  4. I did not find any error in the log either did you integrated any updates? WMF?
  5. It's tiny update nonetheless, i'll see if i have time to update both
  6. I'm not familiar with WPI KB3046269 is needed only if you integrate offline KB3125574 or kb3172605 but if you want to do that online, then KB3177467 is enough yes, specially online, because both are exclusive updates and require no other pending updates and i think 2685811, 2685813 could trigger the pending status
  7. No it doesn't 2685811 &13 are Driver Framework updates you don't need 3046269 if you use 3177467 make sure you put 2533552, 3177467 to be installed first (before 2603229, 2685811, 2685813)
  8. Updated .NE 4.6.1 addon since no update for .NET 4.6.2 so far
  9. For now, and since it's special exclusive update, KB3177467 does not supersede KB3020369 and if you uninstalled/did not install KB3020369, WU will request KB2533552 explicitly (in addition to the famous SP1 entry) i don't know if KB3188988 is useful or not, but as i said about KB3184143, i take is as reqular USB update btw, KB3188988 require KB3020369 as prerequisite
  10. It's recommended, but optional take it as any regular update that contain newer version of the components, such as UAC, Shell32, Explorer
  11. Yes i know Download Center Links takes few days to follow last month, IE11 cumulative released on DC was older version than the actual WU one, and it took them two days to fix it
  12. MU catalog reflect same WU links http://catalog.update.microsoft.com/v7/site/Rss.aspx?q=KB3172605 http://download.windowsupdate.com/d/msdownload/update/software/updt/2016/09/windows6.1-kb3172605-x86_ae03ccbd299e434ea2239f1ad86f164e5f4deeda.msu http://download.windowsupdate.com/d/msdownload/update/software/updt/2016/09/windows6.1-kb3172605-x64_2bb9bc55f347eee34b1454b50c436eb6fd9301fc.msu
  13. The update is released to MU catalog only for now maybe next week it's pushed for WU, or they will wait until next patch tuesday to release the monthly win32k.sys security update
  14. Non superseded by today's updates, except IE11 KB3155178 is superseded by KB3161102 (Journal remover)
  15. It should replace all .net 4.6.1 updates, but i didn't verify that online
  16. You can, but i think it would cause confliction issues and you will have two entries in "Programs and Features" ------------ as for the absolute path "C:\Windows\" in addon, this is restriction be microsoft already tested, you can change some to %windir%, but changing them all will cause the pack to have errors or fail some REG_SZ values will not take variables other than that, Windows OS always defaults and recommended to C: whom want to force other drive letter, should expect errors
  17. Because KB3172605 does not supersede all KB3161608 components with new versiononly some components have newer version, but the rest are the same as KB3161608 (specially WU Client components) and for CBS stack, this makes whole KB3161608 not fully superseded but of course, in the term of rollups, KB3172605 replaces KB3161608 this is similar to Windows 10 cumulative updates mechanism each new cumulative contain whatever the previous cumulatives have + new components or newer version for some components
  18. Convenience rollup KB3125574 supersede both WU client .cabs and WU client update KB3138612 similarly, June 2016 rollup KB3161608 supersede them both as well yes i know that WU checks the state of WUClient-SelfUpdate .cabs on each search session but it completely runs fine without them, and WU itself mention that they are not required WindowsUpdate.log -> SelfUpdate is NOT required. however as usual WU mess, it asks for KB3138612 because it's GDR, while KB3125574 & KB3161608 are LDR that's the same reason why around 8 old security updates show up in WU after installing KB3161608
  19. Yes but technically, WMF can be integrated without .NET 4.5, but will not function
×
×
  • Create New...