Cumulative Update KB4103721 Windows 10 v1803 Build 17134.48 - May 8

adrianArg · 14 May 2018

jyusa said:

Attachment 188139
Attachment 188140

Anybody experiencing this? Build says 17134.48.

Do we have a fix?

I was having a similar error, I attempted to install it like 15 times, I tried everything, deleting the Software Distribution files, a Windows Update fix exe from Microsoft, etc.

Finally I noticed there was some funny business going on with the Windows Insider Program, I never opted in but the option to opt in was greyed out, which I found weird, like if I couldn't do it now or it was already activated.

I followed these instructions to disable Windows Insider from a group policy: Enable or Disable Insider Build Settings in Windows 10

I restarted my PC and I was able to install it.

I have no idea what did the trick (I really doubt it was that last change.. who knows) but it finally worked.

slicendice · 15 May 2018

Cliff S said:

Really guy's, this is the most stabile version & build of Win10, I ever had(not showing off, just showing
Attachment 188699

Normally I should have a few background systemAttachment 188700 fartsAttachment 188700 already, but until now, nothing.

This is what I get:

Cumulative Update KB4103721 Windows 10 v1803 Build 17134.48 - May 8-reliability_17134.48.png

On other computer...NOTHING, but this has been the most unstable Windows 10 release, ever! :)

Cliff S · 15 May 2018

slicendice said:

This is what I get:

On other computer...NOTHING, but this has been the most unstable Windows 10 release, ever! :)

Have you tried running:

fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:&Dism.exe /online /Cleanup-Image /StartComponentCleanup&sfc /scannow&Dism.exe /Online /Cleanup-Image /RestoreHealth&sfc /scannow&Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase&pause

slicendice · 15 May 2018

Cliff S said:

Have you tried running:

fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:&Dism.exe /online /Cleanup-Image /StartComponentCleanup&sfc /scannow&Dism.exe /Online /Cleanup-Image /RestoreHealth&sfc /scannow&Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase&pause

Nope, but running it now.

Scottyboy99 · 15 May 2018

slicendice said:

This is what I get:

On other computer...NOTHING, but this has been the most unstable Windows 10 release, ever! :)

we have two machines. I used to get a smattering of these red marks but since this feature update barely any. But despite this for me personally it’s a bad release. One machine seems to enjoy turning itself on randomly after shut down. Never did this before and there are no alarms or wake up timers set. Seeing as it’s our low end living room box I just ignore it as it doesn’t happen too often. But the ‘family features . Something went wrong’ error box that pops up without fail after every cold boot or restart on both machines is irritating the hell out of us. We rely heavily on family and have user accounts for each child and adult setup on both PCs. Guess most don’t use family setups and multi user accounts to of noticed this but I’ve seen it on a few other friends machines to suggest MS has hosed this up to some degree. Unfortunately this error / aesthetic bug alone is enough to make me really dislike this ‘update’! Really dislike that the useful Cortana interests are gone too. That was so useful to click Cortana and get useful info about weather, headlines, work journey, schedule for my favourite sports team all in one box. Action Center feeds none of this info. Even the main MS edge page has a watered down ‘feed’ now with just news boxes now, no weather or sports fixture schedule. Why do MS change things for sake of change.

slicendice · 15 May 2018

@Cliff S

slicendice said:

Nope, but running it now.

One of the operations crashed. Hahaha!

I need to script this, so that I know what phase did what and what the results were. Having a bunch of commands glued together with & does not say much when reviewing the results. :)

slicendice · 15 May 2018

Alright! Progress!

I downloaded latest Realtek Audio Codec and replaced the one coming straight from Asus. Now ICEsoundAPO64.dll version is 1.0.0.29 (was 1.0.0.19) and does not crash anymore. ...at least not at bootup. :)

Now to testing my BT headsets, to see if that also fixed my connection stability issues. :)

UPDATE: No change in BT headset connection reliability. Still working only a fraction of the time.

Access Denied · 15 May 2018

slicendice said:

Alright! Progress!

I downloaded latest Realtek Audio Codec and replaced the one coming straight from Asus. Now ICEsoundAPO64.dll version is 1.0.0.29 (was 1.0.0.19) and does not crash anymore. ...at least not at bootup. :)

Now to testing my BT headsets, to see if that also fixed my connection stability issues. :)

UPDATE: No change in BT headset connection reliability. Still working only a fraction of the time.

Testing my BT headset and it seems fine. I will report back in couple hours how it goes.

slicendice · 15 May 2018

Access Denied said:

Testing my BT headset and it seems fine. I will report back in couple hours how it goes.

I think I have a beamforming/warm up issue with the headsets on Windows. After being connected for a while, they work flawlessly. :)

Access Denied · 15 May 2018

slicendice said:

I think I have a beamforming/warm up issue with the headsets on Windows. After being connected for a while, they work flawlessly. :)

Mine is working just fine, but the audio quality compared to my 7.1 USB headset is pure garbo

Spoiled myself with that 7.1