New
#240
what wacom model do you have?
Ummm, that's what I said . . . from my earlier post:
it could be a clean install will fix the problem.Note: If there are things wrong in Build 14342 (your tablet wouldn't work), and you update to Build 14352 and things are still wrong (your tablet still didn't work), then as I said, the problem transferred from Build 14342 to Build 14352. In this case, a clean install of Build 14352 did fix the problem. Which is what I advised you to do.I've found that "nasties" in one Build can sometimes transfer to the next updated Build and only a clean install will fix the issue.
I can agree for the most part with nothing will ever top a clean install. And problems do get carried over from build to build at times since that is still an upgrade type install regardless of it now being seen by way of the WU. But I have also seen following build fix what was broken as well.
With the Windows sounds function the 291 was spotless and the 295 decided to trash things and was carried over still to the 316 and on 328 the time came for the full reinstall of the sound care wares which cleaned most of that up. The subsequent 332 upgrade in progression however resolved the Windows sounds playback issue while still needing to see a software reinstall as with the 342 and now 352 build.
Tablets can be a bit touchy at times since the OS is often the embedded type unless on the idea of how the Netbooks worked as far as being somewhat flexible with OSs. Embedded OSs tend to be smaller in size from having various things(the fat) cut away from the OS in order to work on the limitations imposed by the hardwares.
When upgrading from build to build you also have to remember the DiskCleanup will be needed due to the limited disk space available. Too much space taken can mean a degree of paging/swap file issues even on the 64bit when that is present. And you are no longer on mech drives but Static memory.
Well, of course. :) For the most part, that was a reply to the OP because he said I was wrong in my assessment of the problem potentially being carried over from the prior Build. And then went on to say that a clean install had solved the problem, which is what I had advised in the first place. To carry it further, one should never make an absolute statement in the realm of computers! I really shouldn't have said, the problem transferred from Build 14342 to Build 14352. I should have added that it most likely transferred.
So, we're in full agreement on that.
I've been required to install sound drivers on occasion (can't remember the builds), but that's all up 'til now. Saturday when several of us were in a Skype for Business meeting, sound would cut in and out for me. Video was fine. Two of us have the same headset (Bluetooth Logitech H800) and he's had his several years longer than I have.
While in the meeting, which can last more than two hours, we mute our mics when, say, eating a handful of chips and don't want to "crunch in the others' ears". During the course of the meeting I mute my mic (even when I take the headset off) several times.
However, the muting of sound wasn't due to a specific "muting". As I said, the voices would cut in and out, so I'm not wholly sure what I experienced is the same as what others are experiencing. Hmmm, I guess I should copy this to the thread this is being discussed in.
Having only had experience with a Wacom several years ago, specifics as to these kinds of tablets are pretty much lost on me; I can only speak in generalities.
My disk space isn't unlimited by any stretch of the imagination; however, I probably won't ever fill up the 240GB partition with my Insider Builds because I run a rather spare system, installing only those apps I regularly use and a few I want to test with Windows 10.
Thanks for adding solid information to my post. It's greatly appreciated.
I have touch and go on the sound the second desktop sees there while that is with Skype using the onboard since the mini tower never saw a separate card added in. Been trying to get sound going where I carry over sound from the main as well as getting it working on Skype for anything live that comes up.
As far as anything "Sure Fired" especially when running anything developer related there is no such thing! except you can encounter any type of problem at any time! They don't call it "testing" builds for no reason at all! It was actually the 10240 and TH2 Update to be proved the most buggy out of all seen here so far. At least I got two months out of the update however before that went foobar alley.