KB4556799 CU Win 10 v1903 build 18362.836 and v1909 build 18363.836 Win Update

Page 16 of 17 FirstFirst ... 614151617 LastLast
  1. krzemien's Avatar
    Posts : 607
    Windows 10 Home x64
       #150

    ...so it's perhaps lousy drivers' specification and verification / validation process that OEMs are able to circumvent easily?

    (how many have we had these over the years? This is most recent change: https://techcommunity.microsoft.com/...y/ba-p/1389785)

    But also on the other hand: why 1909 release would work absolutely fine with the latest Samsung NVMe driver - as such this driver has been released to masses and Windows allows installing it either - whereas 2004 would suddenly start having problems?

    KB4556799 CU Win 10 v1903 build 18362.836 and v1909 build 18363.836-image.png

    What has changed in I/O domain so significantly lately?

    Why don't I have the same problem with my dated AMD driver?

    I detect lack of integrity here, dear Watson.
      My Computers

  2. sygnus21's Avatar
    Posts : 4,303
    Win 10 Pro (x64) 1909 18363.836
       #151

    Again, whether you agree or not, some hardware will require new drivers. As for why's a and how's, Only Microsoft can answer that.

    And I didn't say I liked it either, I'm simply saying this is par for course and is nothing new.

    Peace:)
      My Computers

  3. CountMike's Avatar
    Posts : 17,029
    W10 Insider + Linux
       #152

    Kbird said:
    I have read Samsung's drivers are causing Issues in 2004 too and assume that is why M$ has blocked 2004 on my computer with a Samsung 970 NVME Drive....

    KB.
    If those drivers were an impediment, forced update would not work either and MCT gave them clean bill of health. It's that damn staggered update that's deciding who gets it in most cases. Problem is in finding what's holding up date up. Only people that got info that 2004 will be available when HW/driver is compatible can have a hint but even that doesn't state which one.
      My Computers

  4. CountMike's Avatar
    Posts : 17,029
    W10 Insider + Linux
       #153

    sygnus21 said:
    Again, whether you agree or not, some hardware will require new drivers. As for why's a and how's, Only Microsoft can answer that.

    And I didn't say I liked it either, I'm simply saying this is par for course and is nothing new.

    Peace:)
    It's WDDM 2.7 requirement that MS tries to enforce, not actually HW itself.
      My Computers

  5. sygnus21's Avatar
    Posts : 4,303
    Win 10 Pro (x64) 1909 18363.836
       #154

    Whatever it is the bottom line is new drivers

    Movin on.
      My Computers

  6. CountMike's Avatar
    Posts : 17,029
    W10 Insider + Linux
       #155

    sygnus21 said:
    Whatever it is the bottom line is new drivers

    Movin on.
    Yup. For better or worse, I got my 2004 forced in with 1909 backup still in reserve.
      My Computers

  7. storageman's Avatar
    Posts : 946
    Windows 10 Pro 2004 19041.329
       #156

    CountMike said:
    Yup. For better or worse, I got my 2004 forced in with 1909 backup still in reserve.
    I glad I'm not the only one that got this FORCED FEATURE UPDATE. Mine happened Sat AM.
      My Computers

  8. sgage's Avatar
    Posts : 1,084
    Windows 10 Pro (Build 18362.418)
       #157

    krzemien said:
    ...so it's perhaps lousy drivers' specification and verification / validation process that OEMs are able to circumvent easily?

    (how many have we had these over the years? This is most recent change: https://techcommunity.microsoft.com/...y/ba-p/1389785)

    But also on the other hand: why 1909 release would work absolutely fine with the latest Samsung NVMe driver - as such this driver has been released to masses and Windows allows installing it either - whereas 2004 would suddenly start having problems?

    KB4556799 CU Win 10 v1903 build 18362.836 and v1909 build 18363.836-image.png

    What has changed in I/O domain so significantly lately?

    Why don't I have the same problem with my dated AMD driver?

    I detect lack of integrity here, dear Watson.
    Surely my dear Holmes, the game isn't worth the candle! By happy chance, I am not a gamer, so I just use Linux. Windows came preinstalled on this computer, so I check it out from time to time, and keep it updated. Plus I've been using Windows since 1992 - inertia, you know. But it's not my main OS.
      My Computer

  9. CountMike's Avatar
    Posts : 17,029
    W10 Insider + Linux
       #158

    storageman said:
    I glad I'm not the only one that got this FORCED FEATURE UPDATE. Mine happened Sat AM.
    Just to make sure we understand each other, It was ME that FORCED update by downloading an using ISO. Didn't get even a message that I might get it thru WU.
      My Computers


  10. Posts : 2
    Windows 10 20H1
       #159

    @Barman58

    Thanks for your reply.
      My Computer


 

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 09:14.
Find Us




Windows 10 Forums