[OFFICIAL] Windows 10 - 19H1 - RTM

Discussion in 'Operating Systems' started by Extraordinary, Mar 28, 2019.

  1. bobmitch

    bobmitch Master Guru

    Messages:
    433
    Likes Received:
    27
    GPU:
    EVGA RTX 2080 TI XC
    The green check mark is there when the printer is ON. When the printer is OFF, it doesn't show at all. Used to be that when it was under Printers...the XP-960 was always there...but grayed out when not on and the icon was not grayed out when the printer was on. So now...when the printer is off...doesn't even show up. That's OK...but I am more concerned with the fact that Microsoft fixed the issue where even though the printer was ON, it showed offline and I couldn't print...had to reboot or turn the printer off and on again to get it online. They fixed this issue, which was pretty widespread, with a patch in early October....now it's broken again. Wish they could fix things permanently. Before the September patch to .418, never had ONE issue with the printer.

    BTW...if I hook the printer up to my laptop, which has Win 10 1803 on it (because 1809 and 1903 both break software that I use for business), the printer shows up properly in Printers and Devices...and works 100% of the time...never have to worry about being online or not. This has been a long standing issue since patch that made 1903 (18362.418) and was fixed next patch and now broken again. I wonder if they have a different team on updates or they are just no longer paying attention.
     
    Last edited: Nov 10, 2019
  2. mbk1969

    mbk1969 Ancient Guru

    Messages:
    8,544
    Likes Received:
    5,432
    GPU:
    GeForce GTX 1070
  3. bobmitch

    bobmitch Master Guru

    Messages:
    433
    Likes Received:
    27
    GPU:
    EVGA RTX 2080 TI XC
    The CLC 280 is connected to USB 2.0 hub. It is "unspecified" as well. My mainboard only has two usb 2.0 ports in the rear...keyboard and mouse. I think Microsoft has made external peripherals "removable" at all times...

    I don't care where the peripherals show up in Control panel. They show up properly in Device Manager. What I want back is 100% peace of mind that when I turn my printer on...it's online. It always had been until patch 18362.418...then Microsoft did something that a lot of people complained about...their printers weren't online anymore. Patch 18362.448 fixed it...everything back to normal...then .449 has broken it again.

    BTW...people with Win 10 1909 (18363.449) are having same issues with Printers and Devices...
     
    Last edited: Nov 10, 2019
  4. mbk1969

    mbk1969 Ancient Guru

    Messages:
    8,544
    Likes Received:
    5,432
    GPU:
    GeForce GTX 1070
    Which USB 3.0 controller - Intel, AMD, ASMedia?
     

  5. bobmitch

    bobmitch Master Guru

    Messages:
    433
    Likes Received:
    27
    GPU:
    EVGA RTX 2080 TI XC
    I am 99% sure Asmedia. The two front ports on my case are connected to a 3.0 hub on the board (Intel) and I believe all but ONE ports in the rear are Asmedia. Printer on Intel

    A person on Ten Forums did a total clean install of Win 10 1903. Did all the updates...to .449 and installed their printer. When done...printer was under "Printers"...closed out Control panel...rebooted...went back in and printer got relisted as "Unspecified"
     
  6. mbk1969

    mbk1969 Ancient Guru

    Messages:
    8,544
    Likes Received:
    5,432
    GPU:
    GeForce GTX 1070
    https://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html
    Have you tried to install (modded) Intel drivers (from that forum)?
    Have you tried to install ASMedia drivers?
    Have you tried to update firmware of ASMedia controllers?
     
  7. bobmitch

    bobmitch Master Guru

    Messages:
    433
    Likes Received:
    27
    GPU:
    EVGA RTX 2080 TI XC
    [​IMG]

    The ones installed are from 2016. When I try to install newer ones...I get message that the correct ones are already installed. Will try one of these and see what happens...Same old same old...
     
    Last edited: Nov 10, 2019
  8. mbk1969

    mbk1969 Ancient Guru

    Messages:
    8,544
    Likes Received:
    5,432
    GPU:
    GeForce GTX 1070
  9. bobmitch

    bobmitch Master Guru

    Messages:
    433
    Likes Received:
    27
    GPU:
    EVGA RTX 2080 TI XC
    Appreciated...but up until Win 19 1903 (18362.418 and again 18362.449) never ever had an issue with USB 3.0...in addition...issue with printer is on Intel USB 3.0

    Not very scientific, but tried something. Directly connected the printer to my laptop (all Asmedia USB 3.0). Powered up and it is online. Seems that if I boot up my desktop with the printer on...it will be online. With the laptop...booted up (Windows 10 1803), and turned printer on....online. It is the two updates from Microsoft .418 and .449 that effect being online. In EVGA forums, others had same issue as I. .448 cured it and .449 broke it again.
     
    Last edited: Nov 10, 2019
  10. mbk1969

    mbk1969 Ancient Guru

    Messages:
    8,544
    Likes Received:
    5,432
    GPU:
    GeForce GTX 1070
    And I tried to install modded Intel USB3 drivers at work rig and they provided much more robust speed with USB drives. May be not to solve the issue with printer, but to try and increase performance.
     

  11. PQED

    PQED Active Member

    Messages:
    69
    Likes Received:
    12
    GPU:
    MSI 1070 Gaming X
    I'm guessing it uses DISM in some part, but I really can't say with any certainty.

    Whenever I've repaired problems myself using DISM I've had to provide a local source as the "online" commands never work (no idea why, even following guides like this).
    I know I'm not alone in having that problem either.

    SFCFix luckily got all of them this time though (still had to fix some errors manually in the past), so it saved me some time and effort this time around.
    I should point out that this happened a couple of weeks ago, I just haven't gotten around to posting about it until now.

    I know I'm supposed to be on 449 by now, but for whatever reason that update still hasn't been pushed to my system.

    But the question remains: how did my system get corrupted again despite doing nothing? Why does it manifest itself as a DPC issue?

    There's nothing apparently wrong with my hardware that I've been able to discern, and last time this problem popped up I wasn't alone in having it either; as I noted in my older posts.

    I'm not expecting anyone to have the answer to these questions, it just feels like Microsoft's updates are breaking more than they're fixing nowadays.

    For anyone interested in what SFCFix repaired most recently; here's an excerpt from CBS.log:
    Code:
    2019-10-29 11:11:47, Info                  CBS    Checking System Update Readiness.
    2019-10-29 11:11:47, Info                  CBS  
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\MSFT_MpComputerStatus.cdxml
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\MSFT_MpThreat.cdxml
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\MSFT_MpThreatCatalog.cdxml
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\MSFT_MpThreatDetection.cdxml
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\MSFT_MpPreference.cdxml
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\MSFT_MpScan.cdxml
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\MSFT_MpWDOScan.cdxml
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\MSFT_MpSignature.cdxml
    2019-10-29 11:11:47, Info                  CBS    (p)   CSI Payload Corrupt   (w)   (Fixed)   amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c\Defender.psd1
    2019-10-29 11:11:47, Info                  CBS  
    2019-10-29 11:11:47, Info                  CBS    Summary:
    2019-10-29 11:11:47, Info                  CBS    Operation: Detect and Repair
    2019-10-29 11:11:47, Info                  CBS    Operation result: 0x0
    2019-10-29 11:11:47, Info                  CBS    Last Successful Step: Entire operation completes.
    2019-10-29 11:11:47, Info                  CBS    Total Detected Corruption:   9
    2019-10-29 11:11:47, Info                  CBS       CBS Manifest Corruption:   0
    2019-10-29 11:11:47, Info                  CBS       CBS Metadata Corruption:   0
    2019-10-29 11:11:47, Info                  CBS       CSI Manifest Corruption:   0
    2019-10-29 11:11:47, Info                  CBS       CSI Metadata Corruption:   0
    2019-10-29 11:11:47, Info                  CBS       CSI Payload Corruption:   9
    2019-10-29 11:11:47, Info                  CBS    Total Repaired Corruption:   9
    2019-10-29 11:11:47, Info                  CBS       CBS Manifest Repaired:   0
    2019-10-29 11:11:47, Info                  CBS       CSI Manifest Repaired:   0
    2019-10-29 11:11:47, Info                  CBS       CSI Payload Repaired:   9
    2019-10-29 11:11:47, Info                  CBS       CSI Store Metadata refreshed:   True
     
    Last edited: Nov 11, 2019
  12. EdKiefer

    EdKiefer Ancient Guru

    Messages:
    2,378
    Likes Received:
    200
    GPU:
    MSI 970 Gaming 4G
    I don't bother to check SFC scannow but I know I read many guys over at Tenforums and they all had a problem with defender when run it.
    My take is it is nothing to worry about.
     
  13. PQED

    PQED Active Member

    Messages:
    69
    Likes Received:
    12
    GPU:
    MSI 1070 Gaming X
    As stated in my initial (older) post I was running ESET Internet Security (used it for years) at the time when I first encountered this DPC issue (which caused a major disruption, rendering the system unusable in certain situations), which I ultimately solved by switching to Windows Defender.

    Now, still running Windows Defender - changing nothing - the DPC issue returns out of the blue just as severe as the first time. I had no recourse but to look for a solution once again.
    Completely disabling WinDef stopped the DPC issues, which is why I tried switching to BitDefender. Merely turning WinDef off through security settings did nothing. Just like with ESET.

    I wouldn't worry about it either if it didn't once again render my system barely usable due to massive DPC issues. Didn't need Latencymon to know what was happening, it's that severe.
    Nor do I believe this to be an issue specificially with WinDef because of my previous experience.

    Unfortunately I no longer have the logs from the last time it happened, maybe they would have proven useful in tracking down whatever is ultimately causing this.
     
  14. mbk1969

    mbk1969 Ancient Guru

    Messages:
    8,544
    Likes Received:
    5,432
    GPU:
    GeForce GTX 1070
    @bobmitch

    Try to upgrade to 1909 - device list looks different there.
     
  15. Chastity

    Chastity Ancient Guru

    Messages:
    2,145
    Likes Received:
    550
    GPU:
    Nitro 5700 XT
    warlord likes this.

  16. KissSh0t

    KissSh0t Ancient Guru

    Messages:
    7,376
    Likes Received:
    1,631
    GPU:
    ASUS RX 470 Strix
    KB4528760 keeps failing to install for me.
     
  17. Chastity

    Chastity Ancient Guru

    Messages:
    2,145
    Likes Received:
    550
    GPU:
    Nitro 5700 XT
    Did you download the package from WU, or MS Repository? Did you grab 1903 or 1909 version? Which version of OS are you on?
     
  18. LocoDiceGR

    LocoDiceGR Ancient Guru

    Messages:
    2,026
    Likes Received:
    600
    GPU:
    Gigabyte R9 380 4G
    Same here on 1909
     
  19. KissSh0t

    KissSh0t Ancient Guru

    Messages:
    7,376
    Likes Received:
    1,631
    GPU:
    ASUS RX 470 Strix
    Windows downloaded it by itself and it had failed, I then tried cleaning windows update, tried a further 3 times, and also tried installing it manually with the update downloaded from the repository.

    OS is 1909.

    Got a few more things to try before giving up xD
     
  20. Astyanax

    Astyanax Ancient Guru

    Messages:
    4,704
    Likes Received:
    1,396
    GPU:
    GTX 1080ti
    its as someone else mentioned, you've removed a component of windows that WU is updating, and the package aborts when its not found.
     

Share This Page