Can you point me to a link where this is discussed? One of my neighbors recently bought some kind of external mixer, USB interface, with speakers and microphone connected through the mixer. He has a problem with noise in the background, which could be described as "Snap, Crackling and Popping". I was unable to offer any real help.
'Sounds like a hardware problem. The sound of "static" could mean a bad connection, possibly in the USB cable, microphone cable, patch cables between the mixer and power amp, or speaker cables between the power amp and speakers. A bad PC driver is not likely to cause this. You might want to resume this topic in a hardware forum/thread.
I have tried all Windows Operating Systems (WinXP-Win10-20H2) and even assembled my own ISOs,all have the snap,crackle.pop,hiss. All my audio hardware is top notch and it has been running perfect on Linux
This is interesting and very useful to know and I have never noticed as I use either WSUS or WUMT for updating and in some cases manual installation using msu or more often dism to install cab files. The Windows Update via Settings has the major downside of not being able to control it after clicking the button to "check". Obviously it can be done and reverted using snapshots for virtual machines as an example.
We were primarily discussing the supersedence, but at least myself I was looking for reasons for Microsoft to remove the recent CU Preview from being provided as an option. We have at least 2 valid reasons now, unexpected reboots and conflicts with other applications which significantly enough, are Microsoft applications.
So this is not specifically a Windows 19041/2 issue? This is a general "Windows" issue? Reminder: This thread is only devoted to Windows 10 final build 19041/2 issues. If the hardware connections are O.K., and it works with Linux, then what's left? A driver that works with Windows. If we assume the USB port driver is O.K., then perhaps you need a specific device driver for the device that is connected to the USB port. MSFT is not necessarily responsible for that driver. Please contact the manufacturer of the device(s) connected to your USB port(s) for support. EDIT: O.K. So now I'm seeing it's not necessarily about a USB connected device. Something is connected to the S/PDIF audio out. And I don't know if this is an S/PDIF connector from an onboard audio chipset or an externally connected USB audio device with S/PDIF out. So trying to help troubleshoot this has been like trying to hit a moving target. I still suspect that it comes down to a Windows driver. I won't do S/PDIF to Digital Coax, or Toslink. My opinion is that it is an obsolete D/A standard. This is about digital jitter, and you can get plenty of that from S/PDIF transfer. I suggest HDMI.
Sound feels like an afterthought in general on Windows. How hard can it possibly be to send sound to multiple devices at once or specify left channel to one BT speaker and right to a different BT speaker? I have 2 Bose SoundLink Revolve speakers and figured it would be simple to use them as left and right stereo speakers, Nope. I had to use the headphone 3.5 splitter into 2 RCA lines and convert both back to 3.5 and use the speakers as headphones. It works flawlessly but why are such simple things so damn hard?
I know of many people with Ryzen systems experiencing this issue. It seems that some motherboards need some extra voltage to the SB chip - v1.05 instead of the default v1.0 fixes the audio issues for many.
I found two answers to parts of my win 10 slowness problem ---- > 1 - Instead of waiting about 2 minutes for microsoft to allow me to turn my computer off .......... i just pull the plug !!!! 2 - Yesterday i decided to look at what the difference is between win 10 pro and win 10 pro workstation . So i emptyed the .wims in both and then deleted all the duplicates from the win 10 workstation . Then i tryed to empty the dustbin ........... it took 45 / FOURTYFIVE minutes . The solution to that is to delete the dustbin itself and then restart . That takes about 2 minutes . Thank you microsoft .
Before the pandemic, I had a sideline as a DJ. I used two large PA speakers (Behringer, 15 inch woofer, 250 watt class D amp). I originally drove this from the headphone output on a laptop, but switched over to a cheap (+/- $10) USB sound adapter. This goes into a mixer which supports a wireless microphone and feeds out via XLR cables to the PA speakers. I switched over from the headphone output to the USB audio because that way the computer generated sounds (various sounds for incoming messages, whatever) continue to go to the internal laptop speakers, and not to the big speakers. I used to run Windows 10 LTSC on the dedicated laptop, but I recently upgraded that laptop to the latest Windows 10 Enterprise. I have noticed no background static or extraneous noises, but I wouldn’t want this showing up when I do have an actual gig. On the other hand, I am not using any Spdiff or other digital audio. Straight analog audio, stereo signal combined for a mono output. PA use does not require anything approaching high fidelity, just decent sound capable of filling up a large space. My main computer, where I do the prep work (mixing, merging, preparing playlists) just runs out of the onboard audio into an external amp with a pair of good bookshelf speakers (Paradigm Atoms). Latest Windows 10 Enterprise, no snap, crackle or pop.
Pulling the plug isn't going to work very well on a laptop. Especially the newer models where the battery is not removable. Or not easily removable. I have been known to pull the plug on a desktop, but in general that's probably not a good idea. NTFS is much more resilient than the old FAT file system, but still ... On deleting large number of files -- the slowdown is most likely caused by moving the files to the Recycle Bin. Do the "delete" from the command line instead of from File Explorer and see if that doesn't dramatically speed up the operation. Or install Cygwin, and use "rm -rf". Very fast under Windows.
Not recommended, but I've pulled the plug and dropped the battery many, many times. NTFS is resilient and recovery with Chkdsk, DISM and SFC is pretty easy.
You don't seem to be paying enough attention to actually follow the discussion. "Pulling the plug" was first mentioned in post #6216 by case-sensitive, and he was talking about pulling the POWER plug. Quite obvious if you read his remarks. No one in this discussion has talked about "pull a head phone plug" except you.
Yes, I read the two posts as one. Blended the audio issue with a power issue. My mistake, that's why I edited my post to refer to power only. Actually, there was no need for me to respond at all. I see no need for further discussion about audio issues, hardware issues, or Windows issues not specifically related to 19041/2. So I'm done with that.