Jump to content

Recommended Posts

Xanthos
Posted

hi,

 

im really disappointed. i changed my htpc hardware and moved from win7 with emby media center plugin to windows 10 with emby theater 3.0.0

 

shortly after the start or already after installation the computer freeze, only mouse is working. doesnt matter if fullscreen or windowed mode or if playback or just moving around in the menues.

 

Specs:

- Win10 Pro 64bit 1803

- Pentium G4560 (Intel HD graphics 610 with newest driver 24.20.100.6025)

 

any ideas except going back to my old sys? :)

 

 

Posted

Hi, is windows up to date?

Xanthos
Posted

hi, yes "no updated available" drivers are newest as well. (i fresh installed it yesterday). no problems except with emby theater :(

Posted

Can you reboot your machine and see if it happens again?

Xanthos
Posted

n1 :)  tried it already (x10 times)

Guest asrequested
Posted

Beware of the new upgrade. Chrome locks up the computer. Which means you can't use Theater desktop, as it uses chromium. I've been battling it for hours. It's a known very large bug. Hopefully there'll be a fix, soon.

  • Like 1
Tur0k
Posted

Beware of the new upgrade. Chrome locks up the computer. Which means you can't use Theater desktop, as it uses chromium. I've been battling it for hours. It's a known very large bug. Hopefully there'll be a fix, soon.

Thank you for he heads up.

 

 

Sent from my iPhone using Tapatalk

Guest asrequested
Posted

In my case, it only happens on my machine with an i7 7700k (Kaby Lake). I'm using another machine, temporarily, and it hasn't locked up. It's running on an i7 6700k. There's a big driver update for the iGPUs, and it looks like Windows has been adjusted for them, in particular gen 7 and above. As those get the new driver. This machine apparently isn't getting that iGPU new driver. Microsoft had a brain fart.

Guest asrequested
Posted

Someone reported it's fixed in the latest update. I'll check it, tonight.

Happy2Play
Posted

Interesting as it all my Windows 10 machines are getting 1803 right now.

Guest asrequested
Posted

Looking good. It looks like Cumulative Update KB4103721, has fixed the problem :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...