Bork Tuesday, Any Problems Yet?

Discussion in 'other software & services' started by Daveski17, Nov 12, 2014.

  1. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    2,933
    Thank you Stupendous Man for your great explanations, tips and advice (here and in the PM) :thumb:

    OK, I installed .NET Framework 4.7 via WU (on Win 7 64-bit) . I thought I'm going to try that first without first installing d3dcompiler_47.dll manually. I was just curious.
    I have a file integrity checker NISFileCheck. Before and after the installation of .NET Framework 4.7 I let NISFileCheck make a database of all .dll files, and before and after the installation I filtered its database for all d3dcompiler_47.dll files on my C-drive and exported those data to a text file. I compared those two text files and they are exactly the same.
    Here is the info for one of the d3dcompiler_47.dll files just to give an idea of the info I get from NISFileCheck:

    Application: c:\windows\system32\d3dcompiler_47.dll
    Status: Unchanged
    Version old: 6.3.9600.18611 (winblue_ltsb.1
    Size old: 3550208
    Date old: 2017-04-28 00:50:12
    RMD160 Hash old: C8ED56869C48CBA7BDA4B63D16CD75DBE508E67D

    Here are more checksums for it:
    The file c:\windows\system32\d3dcompiler_47.dll has the following Checksum(s)
    MD5 - 960AE99A15B1C8C9FBDDDE97606478F9
    SHA-160 - 0C856BA7367E719466ADB73227C39DFFEADDDE27
    SHA-256 - E3009E3738FAB1F7CD685567C5AA1EB0A408AC51D0CDA5DA788841174D7625B1

    Now also look at the special installer for d3dcompiler_47.dll which I manually downloaded (just in case):
    windows6.1-kb4019990-x64_35cc310e81ef23439ba0ec1f11d7b71dd34adfe5.msu
    Look at the date it was digital signed by MS : 28 April 2017
    That is the same date as noted above in that info from NISFileCheck.

    What are your checksum(s) and date for c:\windows\system32\d3dcompiler_47.dll ? (check for just one of those checksums).
    Is my conclusion right that I didn't need to install the special installer for d3dcompiler_47.dll ?
    If I'm right, I guess that I had already it. Why I'm not sure; I guess it had come with a previous update.

    It also looks like that I'm lucky with respect to the Windows Features list (Turn Windows Features on or off).
    It looks like it works.

    I hope that I'm right with the conclusions.
    Stupendous Man, thanks again :thumb: :thumb:
     
    Last edited: Dec 1, 2017
  2. itman

    itman Registered Member

    Joined:
    Jun 22, 2010
    Posts:
    5,486
    Location:
    U.S.A.
    This is an IE11 update.

    There is also something strange about it. It installed fine on Win 10 1709. After installing and rebooting, I immediately re-enabled metered connection for my Ethernet adapter. I then noticed that KB4051963 was trying to download again but the resetting of metered connection blocked it in process. I then checked for Win Updates again and none were available.

    Appears to me that Win Updating is now possibly borked on ver. 1709.
     
    Last edited: Dec 1, 2017
  3. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    1,634
    Location:
    the Netherlands
    If .NET Framework 4.7 was offered via Windows Update, then I suppose d3dcompiler_47.dll was already present, as the June 13, 2017, .NET Blog article Microsoft .NET Framework 4.7 is available on Windows Update, WSUS, and MU Catalog, ".NET 4.7 DirectX dependency" section says:
    "The .NET Framework 4.7 update for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2012 require the DirectX dependency (%windir%\system32\d3dcompiler_47.dll) to be present before .NET 4.7 will be offered to the PC."

    On one of my Windows 7 x64 systems, D3DCompiler_47.dll was installed manually on May 9th.
    The D3DCompiler_47.dll installer, Windows6.1-KB4019990-x64.msu, that I downloaded May 4th and ran May 9th, was signed April 28, ‎2017, 20:37:30.

    On the other Windows 7 x64 system, D3DCompiler_47.dll was installed as part of the June 13, 2017, Monthly Rollup.

    For C:\Windows\System32\D3DCompiler_47.dll the file date and file version are the same on both systems.
    File date April 12, 2017, 15:05:53.
    File version 6.3.9600.18611 (winblue_ltsb.170222-0600)

    I use HashMyFiles to get checksums.
    For C:\Windows\System32\D3DCompiler_47.dll the checksums are identical on both systems.

    However, my checksums are different from what you reported.
    Yours:
    Code:
    MD5       960AE99A15B1C8C9FBDDDE97606478F9
    SHA-256   E3009E3738FAB1F7CD685567C5AA1EB0A408AC51D0CDA5DA788841174D7625B1
    Mine:
    Code:
    MD5       dface0e54e6f3fa1dc0092b6b16f390c
    SHA-256   fd3cc271308e1c1fd21821e0ecaf29498edd46839a4a2712b2fab7aa96b755e2
    I have no idea why we find different checksums for C:\Windows\System32\D3DCompiler_47.dll

    Perhaps there is something wrong in how we use NISFileCheck and HashMyFiles??
     
  4. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    2,933
    I have no idea why our checksums are different.
    The RMD160 is from NISFileCheck.
    For MD5, SHA-160 and SHA-256 I used the old CryptoSuite.

    I uploaded C:\Windows\System32\D3DCompiler_47.dll to VT.
    E3009E3738FAB1F7CD685567C5AA1EB0A408AC51D0CDA5DA788841174D7625B1

    I run Win 7 64-bit Dutch.
    Is your Win 7 64-bit?
     
  5. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    1,634
    Location:
    the Netherlands
    Thanks very much, FanJ .
    Good idea. :thumb:

    I uploaded C:\Windows\System32\D3DCompiler_47.dll to VT.
    e3009e3738fab1f7cd685567c5aa1eb0a408ac51d0cda5da788841174d7625b1

    So, it is the same. :)

    Perhaps there was something wrong in how I used HashMyFiles.
    Or perhaps HashMyFiles is nor not reliable?
    I will look into that later.

    Same here.

    Thanks again.
     
    Last edited: Dec 1, 2017
  6. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    2,933
    Glad we have the same ;)

    Where can I download HashMyFiles ?
     
  7. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    1,634
    Location:
    the Netherlands
  8. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    1,634
    Location:
    the Netherlands
    Off-topic:
    I tested HashMyFiles with a series of files, and compared with the VirusTotal results.
    For some files HashMyFiles calculated the correct checksums, but for other files it does not calculate the correct checksums.
    So HashMyFiles seems not to be reliable!
    Pity, as I liked HashMyFiles for not only being digitally signed but also being portable.
    Another time, I'll need to use VirusTotal for calculating checksums, or try DigitalVolcano Hash Tool, which is also digitally signed of course, and successfully tested by others, but DigitalVolcano Hash Tool is not a portable application.

    /End off-topic
     
  9. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    9,327
    Location:
    England
    I did an over the top install of 1709 with the same build and selected to keep my programs.

    KB4051963 is installed now, but I still see event viewer errors. (event id 16392... the BITS service failed to start) so it may have to be a full Win 10 reinstall
     
  10. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    24,834
    Location:
    U.S.A.
    I can confirm this error:

    2017-12-04_085759.png
     
  11. Minimalist

    Minimalist Registered Member

    Joined:
    Jan 6, 2014
    Posts:
    7,563
    Location:
    Slovenia
    If expiration date is really picked up from local resource and WU can't connect to update server, then IDK how MS is going to fix it.
     
  12. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    24,834
    Location:
    U.S.A.
    Maybe 2020 came early for Win7 users like me. ;) :)
     
  13. paranoidboid

    paranoidboid Registered Member

    Joined:
    Dec 4, 2017
    Posts:
    4
    Location:
    US
    UGH, I messed up hard.
    Looking online for a fix to this last night I stopped the WU service, renamed my SoftwareDistribution folder to SoftwareDistributionOLD and restarted the serivce. Seemed to work but I can't see update history list.

    Now that I know this is M$ problem, is it safe to stop the WU service, delete the current SoftwareDistribution folder, rename the old back to SoftwareDistribution and restart the service? I dunno what to do and I am afraid I might mess something up. :(
     
  14. Minimalist

    Minimalist Registered Member

    Joined:
    Jan 6, 2014
    Posts:
    7,563
    Location:
    Slovenia
    I hope not. :) I still plan to use it till 2020.
     
  15. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    24,834
    Location:
    U.S.A.
    pananoidboid, first, welcome to Wilders! Read this blog, and scroll down to Workaround: Disable Microsoft update options section:

    http://borncity.com/win/2017/12/04/windows7-error-0x80248015-in-update-search-dec-4-2017/

    I performed the workaround and this is what I see now:

    2017-12-04_111159.png

    It's a temporary fix, until Microsoft repairs the damage at its end.

    WARNING: this will happen, when you do the above:
    https://www.wilderssecurity.com/threads/bork-tuesday-any-problems-yet.370217/page-141#post-2723023
     
    Last edited: Dec 4, 2017
  16. paranoidboid

    paranoidboid Registered Member

    Joined:
    Dec 4, 2017
    Posts:
    4
    Location:
    US
    Thank you for the welcome but that isn't my problem at the moment, I had already done the old fix. (Rename SoftwareDistribution folder to something else so that when I check for updates it will make a new SoftwareDistribution folder) WU works but I can't see my update history list nor check for Microsoft products.

    I am just wondering if it is wise to stop WU service, delete the new SoftwareDistribution folder, rename the old folder back to SoftwareDistribution and start the WU service again. I am aware that unchecking Microsoft Product is the easy fix but I had already done the rename SoftwareDistribution folder fix. >.<
     
  17. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    24,834
    Location:
    U.S.A.
  18. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    1,634
    Location:
    the Netherlands
    Hi JRViejo,
    Have you tested if you can successfully re-enable "Give me updates for Microsoft products and check for new optional Microsoft software when I update Windows"?
    In 2010, on the Dutch Security.NL, I've seen a case in which that option was lost or otherwise could not be successfully re-enabled after disabling it. Because of that, I am rather reluctant to disable that option.
     
  19. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    24,834
    Location:
    U.S.A.
    Yes, that option has been removed:

    2017-12-04_115555.png
    However, since I manually check for updates (as you can see above), and I'm not looking for any other Microsoft product updates, and/or optional Microsoft software, that option loss is not an issue for me. I have the feeling that whenever Microsoft repairs the damage, that option "might" return, and I'll report it, if it does.
     
  20. paranoidboid

    paranoidboid Registered Member

    Joined:
    Dec 4, 2017
    Posts:
    4
    Location:
    US
    I've decided to leave it alone. My settings window looks just like yours JRViejo, missing the last two check boxes after making a new SoftwareDistribution folder. No real sense in keep messing with it. Only real thing I am missing is my update history. (My Installed Updates page is normal though, showing I installed KB4048957 last month.)
     
  21. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    24,834
    Location:
    U.S.A.
    I believe when you renamed the SoftwareDistribution folder, the View Update History, via the Windows Updates Panel, is automatically cleaned out.

    And yes, your Installed Updates history, via the Control Panel > Programs > Programs and Features > Installed Updates box, does not go away, unless you manually delete something there.

    Leaving it alone is not a bad decision. Microsoft, with the posted uproar over this, could fix it soon... or so we hope. ;)
     
  22. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    1,634
    Location:
    the Netherlands
    OK, thanks for confirming that disabling "Give me updates for Microsoft products and check for new optional Microsoft software when I update Windows" will remove that option entirely.
    I suppose a warning should be in place for those who don't want that option removed.

    Or one would need to restore that option by choosing "Get update for more products" in Windows Update.
    That is how the "Give me updates for Microsoft products ..." was enabled in the first place.
    However, in the 2010 case that I mentioned, after disabling "Give me updates for Microsoft products ...", the option to re-enable it by choosing "Get update for more products" in Windows Update seemed lost.
     
  23. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    24,834
    Location:
    U.S.A.
    Stupendous Man, you're welcome! With a Win7 OS that's 7 years old, and 2 more years to go before Extended Support ends, I don't think Microsoft will institute any warnings, given that they are trying to change all of us to Win10. ;) :D
     
  24. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    1,634
    Location:
    the Netherlands
    I meant in the Borncity.com blog post, and in our posts in this Wilders thread.
     
  25. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    24,834
    Location:
    U.S.A.
    We just did by discussing it. :cool:
     
Loading...