Major bug found in 17134+

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).
In 17134+, Microsoft has enabled a service called "Connected Devices Platform Service". On startup, this service can go insane and cause the desktop to refresh continuously. It took many, many hours to determine the cause. Fortunately, the resolution is quite simple - the service must be disabled. Here's how:

1 - Press Alt-Ctrl-Del to start the service page.
2 - In the bottom right corner of the page, click on the power button, then, while holding down the Shift key, select "Restart".
3 - Start Safe Mode.
4 - Open the system menu, and navigate to Windows Adminstrative Tools->Services and click on it.
5 - When the Services plug-in starts, locate the "Connected Devices Platform Service" item and either double-click it or right click the item and select "Properties".
6 - Open the "Startup type" menu and select "Disabled".
7 - Press "OK", then reboot your system.

After following these steps, your computer should start up normally.

This service exists in builds prior to 17134, but is disabled by default. There is very little information about what the service actually does, but it appears to have something to do with IoT. Why is it now enabled by default? Ask microsoft.

This bug doesn't seem to be happening much right now, but with 17134 now in the Release Preview ring, I suspect it is going to become very common. I have three systems, and they all suffered from this problem.

The thing is, I used these systems for a couple of days after installation before the bug manifested itself, so a working installation doesn't necessarily mean that you're safe.

This has been submitted to Feedback, but with RS4 in Release Preview, I don't know that Microsoft will be able to fix it before the public release, and even if they fix it in a Cumulative Update, it will be useless, because you won't be able to get Windows Update to run.

I am posting this now because, again, I suspect that it may become a major issue, and I wanted to put a solution out. Good luck, all, I hope that you don't experience this problem. It is nasty.

|

Was this discussion helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this discussion?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this discussion?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hi.

I had a similar problem with "Connected Devices Platform User Service_xxx" in build 17133.1. Therefore, the service was not disabled in builds prior to 17134 as you stated in your post.

In my system, I overcame the problem by uninstalling Xbox One app.

High CPU Utilization >

By the way, I have three Windows 10 Build 17134.1 m/c and only one of them showed the anomaly.

Hope this helps.

Have a long and prosperous life.

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I never had the problem before I installed 17134, so I don't know when it was enabled. However, my 16299 has this service and it is enabled. I don't use the Xbox app, so it would never occur to me to uninstall it, but I prefer my method necuase it ensures that the problem cannot recur. 

The "Connected Devices Platform User Service_xxx" is a dynamic service created by "Connected Devices Platform Service", and cannot be disabled or stopped.

K.

No man is satisfied with his fortune, but every man is satisfied with his wit.
- Leo Tolstoy

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Suggest when posting and you say all 3 of your system have this issue post info about your systems, as for mine I haven't seen this issue my system is a custom built with A Q9400 CPU on an intel MB.
I'm a unpaid independent Advisor/volunteer

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I did not se this to ne important in this case. But:

AMD FX-8320 CPU on an ASUS M5A97 R2.0 motherboard with a HyperX 3k SSD, Xonar DX sound card, Corsair XMP-3 RAM, Corsair power supply

The other two are Intel i7-7700s with much the same peripherals.

K.

No man is satisfied with his fortune, but every man is satisfied with his wit.
- Leo Tolstoy

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Ok thanks as my testing system is on the older side so it may be the reason it hasn't had the issue.
I'm a unpaid independent Advisor/volunteer

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I should say that, after surmounting this problem, 17134.1 is the fastest and most stable build of Windows 10 that I have used - and I have used almost all of them.
K.

No man is satisfied with his fortune, but every man is satisfied with his wit.
- Leo Tolstoy

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Quote:

"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).

In 17134+, Microsoft has enabled a service called "Connected Devices Platform Service". On startup, this service can go insane and cause the desktop to refresh continuously. It took many, many hours to determine the cause."

Unquote.

Just out of curiosity, how did you relate "Connected devices platform service" to screen flickering when you couldn't do anything while screen was flickering ?  

In my case, it was easy. I just sorted out the CPU column under Processes tab in Task Manager and Connected devices platform service came out stark naked.

By the way, Connected devices platform service and Connected devices platform user service_xxx can be stopped in Windows. Their startup types just can't be changed from Automatic to Manual or Disabled, though. You get "Wrong or incorrect parameter" warning. But you said they could be disabled in Safe Mode. I didn't try it.

Have a long and prosperous life.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

This bug just happened to me today, 4/23/2018.  I was able to disable it through the task manager under the services tab, and then right-clicking connected devices platform service and choosing "open services" right click connected devices platform service and choose "properties" and in the popup window that comes up you can choose Disable.  Then reboot your system.  This all worked for me and now my system is back to running great again......

Thanks for the tip...

Dennis

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes, I did it that way as well, but when the Task Manager is running on a flashing desktop, it is not so easy to use it. I thought my method might be easier for people who don't know computers that well.
K.

No man is satisfied with his fortune, but every man is satisfied with his wit.
- Leo Tolstoy

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I absolutely concur.  My computer is blazing fast.  Also, with 17334, much "garbage" has been removed as I now have 17+GBs more free space.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Discussion Info


Last updated February 2, 2021 Views 2,285 Applies to: