Windows 10 RTM build 17134 breaks PCs, not ready for public release
Microsoft recently rolled out a new Windows 10 Spring Creators Update RTM build candidate to Slow Ring and Release Preview Insiders, just as we suggested in a previous post. Windows 10 build 17134 is supposed to fix the BSOD errors that initially prevented the Windows 10 version 1803 release.
Speaking of the upcoming Windows 10 OS version, it is still unclear what name Microsoft will use for it. However, recent reports suggest that Windows 10 April Update is probably going to be the new name that the Redmond giant will use for this major OS update.
Unfortunately, we’re not sure that Windows 10 build 17134, the new RTM candidate, will actually be the build that Microsoft will deploy to the general public. Insiders reported this build release is affected by some severe issues that break computers. Indeed, it seems that BSOD issues are gone, but new bugs have arisen.
Under these circumstances, Microsoft may need to push a new build to Insiders in order to fix the bugs affecting build 17134. Yes, this means delaying the Windows 10 April 2018 Update release once again.
Windows 10 build 17134 issues
Insiders can’t boot up their laptops
Some Insiders can’t use their computers after installing the latest Windows 10 build.
From 17133.1 to 17134 after install finish through windows update and restart it,i cannot open my laptop anymore and just revert the updates, i guess something need to fix, or just create the media creation tool already, for me windows update is not working properly for somebody, when downloading there are no ETR. Im pissed now. I follow every single steps, i waited too long but this update, ruined my laptop.
Display flickers on and off
This is quite a severe bug as it makes the troubleshooting process very difficult to complete.
I have discovered a major bug in build 17134 and 17643/17650 which causes the desktop to refresh and flicker on and off very quickly. This makes your computer useless – you can’t run any programs and it makes troubleshooting a challenge (to say the least).
The good news is that you can fix this problem — with a bit of extra patience. Insiders confirmed that disabling the Connected Devices Platform Service and the Xbox One App fixes the problem.
- Press and hold Alt+Ctrl+Del to launch the service page > click on the power button > hold the Shift key and
- Select Restart to enter Safe Mode
- Open the system menu > go to Windows Adminstrative Tools > select Services
- Select ‘Connected Devices Platform Service” > right click on it > go to Properties
- Select ‘Startup type’ > select ‘Disabled’ > hit OK > restart your computer and check if the issue persists.
As you can see, Microsoft still has some work to do in order to release a stable and reliable Windows 10 RTM candidate.
Over to you now:
- Do you think Microsoft will delay the Spring Creators Update again?
- If you’re a Slow Ring/ Release Preview Insider, you can tell us more about your Windows 10 build 17134 experience in the comments below.
RELATED STORIES TO CHECK OUT:
- How to download and install Windows 10 Spring Creators Update
- How to block Windows 10 Spring Creators Update from installing on PC
- Will Spring Creators Update finally fix gaming issues on Windows 10?
Bootloops and BSODs are something every PC user will run into eventually. The important thing is not to panic and try deducing what’s causing the issue. […]
The high CPU usage on a Cisco router is rather uncommon. If you’re configuring routers frequently, you’ll know that CPU utilization will rise when transferring […]
Javaw.exe is a process that launches Java programs. However, a “Windows cannot find javaw.exe” error message can pop up for some users when they try […]