New Windows 10 Insider Preview Fast + Skip Build 18298 (19H1) -Dec. 10 Insider

Well, I am not having any of those problems mentioned here. Sound is okay, VMware is good, Macrium still working.
But this morning out of the blue at sign in time I got a GSOD saying that "Windows Service Exception" Win32KFull.sys.

emilcioran99 said:

In the model page is posted the Realtek Audio Driver V6.0.1.8437 and as I said at the beginig of the discussion , tried already.
Tried 5-6 (older and newer) Realtek drivers. There are no differencies regarding the sound in 18298.


At the end, didn't understand (and seems till now that nobody understands) what is wrong in this build.
What's so different from the previous version to make system at boot to not recognize/see the audio controllers?

Emilcioran99, here's a copy of a post I made on December 12:

Well, folks, I think I found where Microsoft blew up Windows . . . Looky this:



Since it's December 12, it stands to reason the Driver date in the above belongs to Microsoft and not my system. Look at the Driver Provider: Microsoft; Driver Date: 12/5/2015; Driver version: 10.0.18298.1000; Digital Signer: Microsoft Windows

It looks to me like Microsoft updated the driver, but screwed up the installation! Gahhhhhhhhhhhhhhh, so it looks like all you have to do is update the High Definition Audio CODEC, but follow @Andre's instructions.

Editing . . . OK, done editing; had to get the graphic in; it wasn't in my original post when I copied it.

Edit 2: And now we know that there's more wrong with the "new drivers" than I thought. It won't be a simple modification, but I'm pretty sure that's where Microsoft Dev Team went wrong.

kado897 said:

I know it's frustrating but this is beta software and we may never know why it works for some and not for others. The only people who may know the answer are MS and they aren't talking.

At this point, I think the only one taking responsibility for his actions was on Good Morning America this morning. :) Microsoft sure ain't agonna admit nuttin'!

JGToy said:

Well, I am not having any of those problems mentioned here. Sound is okay, VMware is good, Macrium still working.
But this morning out of the blue at sign in time I got a GSOD saying that "Windows Service Exception" Win32KFull.sys.

Although I sometimes get a bit of nastiness out of my Insider Builds, normally, I'm the one who gets to say "everything seems to be working fine for me", but not this time!

That said, I was one of the lucky ones and my sound is now working in Build 18298. <knocking on wooden head> Never have experienced a GSOD nor any of the other problems others are having.

Wynona said:

Although I sometimes get a bit of nastiness out of my Insider Builds, normally, I'm the one who gets to say "everything seems to be working fine for me", but not this time!

That said, I was one of the lucky ones and my sound is now working in Build 18298. <knocking on wooden head> Never have experienced a GSOD nor any of the other problems others are having.

Glad to hear that you got your sound back!

Mine has been OK with this build, the only exception was for the 2 starting ones (it killed my Sandboxie and somehow it ran all my scheduled task), apart from that it is working well (I guess) but the GSOD I received this morning was a surprise.

jimbo45 said:

Hi there @JGToy

I see you have no issues with VMWare on this release unlike many people both here and on the VMWare forums.

Do you have INTEL or AMD CPU as I believe the problem might be related to INTEL CPU IPM / security module or similar.

Please post back as I think a lot of VMware users would love to see this issue moved on a bit as it's the 2nd skippy release where a number of us have encountered problems with VMWare.

For others -- I've no sound issues at all on this release on HP laptop (Intel CPU/Graphics /HD sound). ASpart from the VMWare issue I don't have problems with this release so far.

Thanks

Cheers
jimbo

Hi,

CPU: Intel® Xeon® X5690 3.47GHz Six-Core, you can see the whole computer description at my profile.
It is an old beast but still working pretty good.