If the lockdown wasn't bad enough Windows 10 continues to screw life up

raglafart

raglafart

Limp Gawd
Joined
Feb 21, 2013
Messages
227
I though I had the sound issues well sorted having gone to build 2004, today no more sound on Video clips again, I am seriously over Windows 10 and all the crap you have to put up with.
Really really p!553d off.
Why do I have to keep deleting all the sound outputs that Windows keeps installing and then breaking???????????????
I've got all the sound back, Delete every sound output in the "Device Manager" and then reboot, but for f's sake why??????????????????
 
Last edited:
Over the past 3 or 4 releases I've continued to have an issue where the audio service needs to be restarted to make all sounds stop buzzing. It happens maybe only once every other month but still annoying.
 
I have SoundBlaster ZxR and after every major update my sound output will go to the monitor. The latest update is the worst - now my SoundBlaster Control Panel won't even run when Windows starts, but I can still run it manually. I have to manually switch the default output back to ZxR.

Still sticking with Windows 10 though.
 
I haven't had much any problems with Win10 on the 2-3 times I've used it during the last 2 months. The key must be to use it as little as possible and it won't get broken...
 
B00nie said:
I haven't had much any problems with Win10 on the 2-3 times I've used it during the last 2 months. The key must be to use it as little as possible and it won't get broken...
Click to expand...

The last time I used my Windows PC was to set up a CF HDD for my Commodore Amiga using WinUAE. The rest of the time my wife uses what's effectively a full blown gaming PC for working from home as I've really got little use for it anymore.
 
More updates and guess what, sound is crashed yet again. Come on Microsoft, fix your F ups for once please!
 
What sound card do you have? Onboard or add-on? What are you outputting to? Maybe with some actual information, someone might be able to help you.
 
As much as I like to "rag" on Microsoft, they can't be left to blame for all driver issues. After initial certification (if that happens), vendors update their drivers and no Microsoft vetting is happening.
 
cjcox said:
As much as I like to "rag" on Microsoft, they can't be left to blame for all driver issues. After initial certification (if that happens), vendors update their drivers and no Microsoft vetting is happening.
Click to expand...

This isn't the first time such an issue has occurred regarding Realtek audio...
 
cjcox and Mazzspeed
Your comments would be fine if the drivers were different each time. It has to be a Microsoft issue, it's only when I get the unwanted updates this happens, ever single time they do another update. How can it be a Realtek issue?
 
raglafart said:
cjcox and Mazzspeed
Your comments would be fine if the drivers were different each time. It has to be a Microsoft issue, it's only when I get the unwanted updates this happens, ever single time they do another update. How can it be a Realtek issue?
Click to expand...
Microsoft changes something in the system constantly which requires changes to drivers -> vendors fail to keep up with the changes and things go broken. So Microsoft is the cause and the vendor failure is the effect.

It just seems the development is not controlled enough so it causes unreasonable demands for vendors to maintain their drivers. And it's entirely possible that all changes are not documented either. Microsoft has too large a dominance of the PC market so they think they can do whatever they like. And largely it's true - a large brainless flock of sheep will follow them to the grave.
 
The thing that is really stupid are the new versions every 6 months. Just when they start to fix the bugs, a new version is released that causes all kinds of issues. It would be nice if they waited a full year to release a new version and not force it down your throats for the update. I think each version is good for 24-30 months before you are forced to upgrade.
 
raglafart said:
cjcox and Mazzspeed
Your comments would be fine if the drivers were different each time. It has to be a Microsoft issue, it's only when I get the unwanted updates this happens, ever single time they do another update. How can it be a Realtek issue?
Click to expand...

Last time this issue occurred, it was a Realtek driver issue. Although it has to be stated, Realtek sucks.
 
I think Microsoft changed something audio-wise across the board with the 2004 release. I use Nvidia's HDMI-out and after nearly every reboot, my speaker array defaults back to stereo. I'll be doing some work and audio will randomly stop working. I look back at the control panel, and sure enough, my speaker array has reset itself.
Realtek sucks no doubt, but I think this was at least partially MS's doing. I never had this happen until the 2004 release.
 
Domingo said:
I think Microsoft changed something audio-wise across the board with the 2004 release. I use Nvidia's HDMI-out and after nearly every reboot, my speaker array defaults back to stereo. I'll be doing some work and audio will randomly stop working. I look back at the control panel, and sure enough, my speaker array has reset itself.
Realtek sucks no doubt, but I think this was at least partially MS's doing. I never had this happen until the 2004 release.
Click to expand...
The 2004 Release update, at this time, is an Optional update on my Windows 10 Pro and Home systems. The problems folks are experiencing might be the reason it is Optional.
 
It is only going to get worse as they get more aggressive with the updates. I believe this update that just came out automatically "fixes" any port blocking or other tricks you have deployed to stop any part of the windows update process.
 
vegeta535 said:
I got 99 problems and windows 10 is never one.
Click to expand...
Sometimes that is true and sometimes it was good old Windows.
Have had to rescue a couple of people due to corrupted profiles and other issues with the last couple of updates. The 2004 seems to be holding it was the updates to 1909 that caused problems.
Wish as well they woudl fix the three rebbots needed to finish updates. Why they couldn't have squeezed the .net updates into the 2004 is beyond me. But considering how sloppy the coding is these days, no real surprise.

" It is only going to get worse as they get more aggressive with the updates. I believe this update that just came out automatically "fixes" any port blocking or other tricks you have deployed to stop any part of the windows update process. "

Yep along with turning on Defrag whether you wanted it on or not and messing up backups.
Along with setting Skype to auto start and run all its crazy updates too.
Notice how Adobe and Google have gotten just as pobnoxious with turning on auto updates and checking for updates every hour.

BTW if anyone has a script to turn them back off and discable the services that woudl be great! Been too many years since I've scripted in powershell.
 
You must log in or register to reply here.
Back
Top