KB4541738 for Windows 10 Insider Preview Slow Build 19041.153 March 13 Insider

Page 3 of 3 FirstFirst 123

  1. Posts : 5
    Windows 10
       #20

    When connecting a second monitor Windows does not recognise it as an audio playback device until I restart, anyone knows how to fix this? (NVIDIA High Definition Audio)
      My Computer


  2. Posts : 979
    10 + Linux
       #21

    hairycoconut said:
    When connecting a second monitor Windows does not recognise it as an audio playback device until I restart, anyone knows how to fix this? (NVIDIA High Definition Audio)
    Is select playback device available on the volume control for duplicate or second screen only (WIN + P)?
      My Computer


  3. Posts : 5
    Windows 10
       #22

    MikeMecanic said:
    Is select playback device available on the volume control for duplicate or second screen only (WIN + P)?
    What's happening is that Windows is deleting the playback device of the monitor you choose not to display in the Windows+P dialog, PC screen only it deletes the second monitor playback device, Second screen only it deletes the first monitor playback device.

    But the worst is that it does not automatically find these devices later on extend/duplicate, you need to actually restart the computer or plug the monitor in a different port.

    One other bug is that context menus are opening to the left by default on a new installation.
      My Computer

  4. Brink's Avatar
    Posts : 56,482
    64-bit Windows 10 Pro for Workstations build 21364
    Thread Starter
       #23
      My Computers


  5. Posts : 94
    Windows 10 Pro 64bit (Insider Builds)
       #24
      My Computer

  6. Brink's Avatar
    Posts : 56,482
    64-bit Windows 10 Pro for Workstations build 21364
    Thread Starter
       #25
      My Computers


  7. Posts : 114
    Windows 10 V1709
       #26

    fg2001gf10F said:
    This bug is fixed in latest 20H1 Builds in the Fast ring, but the fix was never propagated to the Slow ring Build 19041.153 which still fails solid with some USB attached SCSI devices. This device cannot start (Code 10) (Not Enough quota)

    iDsonix is one example of failing enclosure which works fine with current public build 18363.720 or with Insider Build 19582.1001, but fails with 19041.
    See error in pictures below:

    Attachment 270311 Attachment 270313 Attachment 270312
    This (Code 10) Device cannot start error has been fixed with Build 19041.173 on 04/09/2020.
      My Computer


 
Page 3 of 3 FirstFirst 123

  Related Discussions
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 21:08.
Find Us




Windows 10 Forums