Topic: Windows 10 Start Menu and Modern Apps 'problem' - superseded (Read 28329 times)

terrym@tassie · « **Reply #50 on:** September 16, 2017, 09:55:51 pm »

Can I just reiterate, if you have problems with w10spk please send me a Personal Message, I can then help you.
Otherwise this thread can become very long.
Terry

imeric · « **Reply #51 on:** September 18, 2017, 11:14:59 am »

Quote from: DocLotus on September 16, 2017, 02:37:49 pm

That resolved a lot of long time problems I have been having with MC for the last three years or so.

Thanks;
Doc

Hi Doc, Would you mind sharing your list or point me where it is?

MC23 has been very stable from day one for me but if upgrading to 64 bits makes it even better why wouldn't go to 64 bits?

(I still get a very rare case where after listening to music and going back to TV will make it hang or crash)
thx

DocLotus · « **Reply #52 on:** September 18, 2017, 01:12:17 pm »

Quote from: imeric on September 18, 2017, 11:14:59 am

Hi Doc, Would you mind sharing your list or point me where it is?

MC23 has been very stable from day one for me but if upgrading to 64 bits makes it even better why wouldn't go to 64 bits?

(I still get a very rare case where after listening to music and going back to TV will make it hang or crash)
thx

Sure...
https://yabb.jriver.com/interact/index.php?topic=112225.0
It's the 5th item from the top.

terrym@tassie · « **Reply #53 on:** September 18, 2017, 06:30:34 pm »

@DocLotus- can you get back to me on the Personal Messages I've sent you re: your issue with w10spk. Thanks

New release of w10spk (V1.1d) attached to the second post of this thread, there is no need to upgrade unless you were getting any issues with Task Scheduler creation/modification when running setup.cmd.

My thanks to stewart_pk for reporting his issue and testing the new update.

Terry

millst · « **Reply #54 on:** September 23, 2017, 01:35:22 pm »

The plugin version has an updated installer for 64-bit MC. You can download it here.

-tm

blackjack007 · « **Reply #55 on:** October 06, 2017, 06:14:00 pm »

When is JRiver going to fix the problems seen after running for a while when using the latest updated versions of Windows 10!? This has been now seen for years and never addressed. Blamed on "a known windows" problem. ... That no other program seems to have.

Issue review ... after running Media Center for a while (happens with 32 or 64 bit versions), start button in windows gets locked, other things crash. We are running latest Windows 10 64bit Version 1703 (OS Build 15063.632)

This does not happen with any other programs. Just Media Center ... and it has been happening for over a year.

Awesome Donkey · « **Reply #56 on:** October 06, 2017, 07:31:02 pm »

Because it's a Windows 10 problem and NOT a JRiver problem. Media Center isn't the only software which can trigger this issue; Steam and Adobe's apps are other examples. I suggest giving feedback to Microsoft and ask them to finally fully fix this issue.

There's several workarounds including the script found in this thread, along with a workaround plugin for Media Center found in this thread. Have you given them a try?

tyler69 · « **Reply #57 on:** October 07, 2017, 02:35:47 am »

Can you link me to some sites that state that other software is not working? I googled steam and Adobe but found only a Microsoft support thread in which someone stated that this was issue fixed by the Windows 10 anniversary update. Maybe I'm just "googling wrong"..

Thanks.

Hendrik · « **Reply #58 on:** October 07, 2017, 02:49:46 am »

It definitely happens for me personally with just Steam.

kalston · « **Reply #59 on:** October 07, 2017, 08:23:05 am »

Yeah, it's surprisingly difficult to find anything about it on the Internet but I've seen it happen with other applications.

I have not seen it happen too often with Steam (depends how you use it maybe or could be some of the settings?) but with MC it's every single time for me on my desktop. On the other hand I've only got the bug 2 or 3 times on my laptop for whatever reason, despite using MC a lot.

I have a "restart explorer" icon on my desktop because of it (only downside for me is that it brings back the language taskbar icon that I prefer to hide... but on the plus side it fixes another bug where the taskbar stays on top in borderless mode).

RoderickGI · « **Reply #60 on:** October 07, 2017, 05:44:55 pm »

Garmin Express does it nearly every time I use it.

pqcgebxm · « **Reply #61 on:** October 08, 2017, 10:46:06 am »

Hi All,

Just found this thread after many attempts to find the cause/solution to this problem. Finally I know it's not just my system! Thanks for the effort to solve this.

I installed the script and it seems to be working for the start and search menus, and also for modern apps. But, there are two other issues which I assumed were related to this overall problem, but which are still occurring:

1. The Action Center menu (the notification icon at the far right) still does not work for me.
2. When I use the search menu to find an app and then click on the app, nothing happens.

Is anyone else experiencing these problems as well? Are they related to the windows/search menu bugs?

Thanks!

terrym@tassie · « **Reply #62 on:** October 08, 2017, 06:31:50 pm »

Quote from: Sinnerman on October 08, 2017, 10:46:06 am

Hi All,

Just found this thread after many attempts to find the cause/solution to this problem. Finally I know it's not just my system! Thanks for the effort to solve this.

I installed the script and it seems to be working for the start and search menus, and also for modern apps. But, there are two other issues which I assumed were related to this overall problem, but which are still occurring:

1. The Action Center menu (the notification icon at the far right) still does not work for me.
2. When I use the search menu to find an app and then click on the app, nothing happens.

Is anyone else experiencing these problems as well? Are they related to the windows/search menu bugs?

Thanks!

I'm afraid the issues you describe are unrelated to the Start Menu becoming unresponsive. They certainly work for me on my systems.

I'm glad the script has sorted your Start Menu etc though.

musana · « **Reply #63 on:** October 10, 2017, 03:38:39 am »

Yesterday I installed JRiver Media Center 23 shortly before supper, and played some music. When I returned to my computer after supper I found that my Start Menu would not open, and the right-click menu on Taskbar buttons did not work.

It was not my first experience with this problem. It happened about a month earlier, when I upgraded to Media Center 23, but on that occasion some time had elapsed between the installation and the Start Menu/Taskbar problems. Although I mentally noted the association of the problem with installing Media Center, I frankly trusted that JRiver would be sufficiently knowledgeable about Windows 10 by now that they wouldn’t release an incompatible product. So I put that out of my mind, and spent days researching and trying various proposed solutions to the problem, unsuccessfully. I finally gave up and completely reinstalled Windows 10. And then spent many more days installing and configuring my applications.

My system was rock-solid until I reinstalled Media Center 23 yesterday. This time, I remembered the association. And so to address the problem I tried uninstalling Media Center.

Problem solved. Start Menu and Taskbar working fine.

I’ve been a user of Media Center since 2004. No longer.

WD

Awesome Donkey · « **Reply #64 on:** October 10, 2017, 04:12:29 am »

It's a well known Windows 10 bug that Microsoft has never fully fixed yet. Look here for more info along with several workarounds: https://yabb.jriver.com/interact/index.php/topic,106925.0.html

There's even a plugin for Media Center which works around this bug. This is what I've been using lately, and it works easily and wonderfully without needing to set anything up except installing the plugin.

P.S. This Windows 10 bug doesn't occur with just Media Center, but other software too including Steam, Adobe's apps and Garmin Express.

tyler69 · « **Reply #65 on:** October 10, 2017, 05:21:00 am »

On my PC this only occurs when running MC. I have steam and adobe acrobat installed and active.

Awesome Donkey · « **Reply #66 on:** October 10, 2017, 05:24:25 am »

I've definitely had it occur when running just Steam, as has Hendrik.

It's just very random. I've had it happen with a clean Windows 10 install without any software installed. So yeah, Microsoft needs to get their stuff together and fully fix this bug.

chris635 · « **Reply #67 on:** October 16, 2017, 02:21:11 pm »

Hi all,

I was going to wait a bit before posting, but I may as well. I have been running the fall creators update build 16299.19 for several days now on two of my machines, and I am not running into any start menu or suspended app issues. I think further testing is required, as I am not prepared to say Microsoft fixed it yet, but so far so good.

Chris

Awesome Donkey · « **Reply #68 on:** October 16, 2017, 02:52:44 pm »

If Microsoft actually fixed this in the Fall Creators Update I'd be EXTREMELY surprised. But I'm not holding my breath unless terrym@tassie says otherwise.

chris635 · « **Reply #69 on:** October 16, 2017, 02:55:19 pm »

I have been in contact with terry and his preliminary testing is good, however long term testing is needed.

Chris

Awesome Donkey · « **Reply #70 on:** October 16, 2017, 02:57:41 pm »

Huh, hopefully he keeps us informed. It'd be GLORIOUS if Microsoft actually finally fixed this issue.

I'm already running the same RTM build too. I suppose I'll remove the script and see what happens.

EDIT: Nope, not fixed as the Start Menu died after 2 hours of continuous music playback (where I purposely didn't click the Start Menu during that time).

terrym@tassie · « **Reply #71 on:** October 16, 2017, 04:44:54 pm »

Quote from: chris635 on October 16, 2017, 02:55:19 pm

I have been in contact with terry and his preliminary testing is good, however long term testing is needed.
Chris

Thanks to chris635 who gave me the 'heads up' on this issue.

The one system I'm testing the 16299.19 preview build on continues to be OK.
No issues with the Start Menu, any suspended (minimized) Universal Windows Platform (UWP) apps restore to maximized and function normally after extended playback of audio via JRiver MC23 x64.

It is still early days but I have to say this is looking extremely promising that Microsoft may have actually fixed the bug.
I'm going to do the 16299.19 update on my HTPC as soon as practicable so I can fully test how it goes with video playback.

At this stage I'm still cautious because I remember the bug on very early Windows 10 builds used to disappear after a build update only to reappear about a week later.
I think I might also update one system to the the Windows 10 'fast' ring 17000 series builds to make sure the bug doesn't reappear.
I also need to do some testing with the 32-bit version of MC23.

Terry

Awesome Donkey · « **Reply #72 on:** October 16, 2017, 04:45:59 pm »

I'm using 16299.19 (aka the Fall Creators Update RTM, a clean install of course) and after two hours of continuous music playback without stopping via ASIO (where I purposely didn't click the Start Menu during that time) the Start Menu indeed "died" like it has in previous releases. Didn't do anything but change the artists/songs in MC23 x64 and browse the Internet with Google Chrome 64-bit. So it's definitely not fixed yet. Also have other apps running in the background, including Steam, which is known to also trigger this issue.

Oh well, hopefully Redstone 4?

terrym@tassie · « **Reply #73 on:** October 16, 2017, 04:58:10 pm »

Quote from: Awesome Donkey on October 16, 2017, 04:45:59 pm

I'm using 16299.19 (aka the Fall Creators Update RTM, a clean install of course) and after two hours of continuous music playback without stopping via ASIO (where I purposely didn't click the Start Menu during that time) the Start Menu indeed "died" like it has in previous releases.

That is very disappointing news!
Perhaps the best we can hope for is that a smaller percentage of systems may be affected by the bug with these newer builds.

Terry

chris635 · « **Reply #74 on:** October 16, 2017, 05:09:04 pm »

I'm continuing testing myself terry. I have three machines running. I will leave them for 24 hours and see what happens. Two of them with ASIO and one with WASAPI.

Chris

chris635 · « **Reply #75 on:** October 16, 2017, 05:13:39 pm »

Let me also note that two of my machines are fresh installs of the creators update and one is an in place upgrade.

Chris

RD James · « **Reply #76 on:** October 20, 2017, 09:51:45 am »

It's far less frequent on the Fall Creators Update, but not fixed. Had it happen again today - though ShellExperienceHost.exe did not appear to be suspended.
I also have an issue now where there's maybe a 20% chance when I reboot the PC that the start menu won't work at all and I have to reboot it again to fix it.

terrym@tassie · « **Reply #77 on:** October 20, 2017, 06:05:37 pm »

Quote from: RD James on October 20, 2017, 09:51:45 am

It's far less frequent on the Fall Creators Update, but not fixed. Had it happen again today - though ShellExperienceHost.exe did not appear to be suspended.
I also have an issue now where there's maybe a 20% chance when I reboot the PC that the start menu won't work at all and I have to reboot it again to fix it.

Yes, it is far less frequent but the 'bug' is still there. However it is a vastly improved situation as the 'bug' now ONLY affects the Start Menu and Search/Cortana, any suspended UWP apps or items like Systemsettings will work normally and recover from being suspended. I have to date on the systems I have upgraded not encountered the issue of the Start Menu not working after a reboot.

I have in beta testing at the moment a solution to the 1709/16299 Start Menu issue which leaves the UWP apps working as they should, it also contains an option that would allow the recovery of the Start Menu if it fails after a reboot which would fix it without the requirement to boot again.
It is also backwards compatible with the previous builds of Windows 10 (1703,1607 etc).

If anyone else is interested in participating in the beta testing of w10spkV2 please send me a Personal Message.

amsco15 · « **Reply #78 on:** October 21, 2017, 09:57:30 am »

The latest Win 10 update seems to have solved the problem on my machine. Still early to declare total victory but start, search and settings have survived two lengthy listening sessions. First time that’s happened in years.

Awesome Donkey · « **Reply #79 on:** October 22, 2017, 12:20:45 pm »

It's likely still there, but takes longer to show itself. I'm testing Terry's updated w10spkV2 script and it's been working wonderfully with the Fall Creators Update thus far.

cfrab · « **Reply #80 on:** October 22, 2017, 04:05:53 pm »

hello
I'm using MC 23.0.72 on win10 release 1703.
I experienced the issue of "start menu become unresponsive" during MC playback, solved by installing the w10spk script as described in this thread.
Unfortunately, now I found the same issue when using Media Server (run on win10 startup); the w10 start menu become unresponsive after a while when controlling playback from Media Server with Gizmo (android) or other DLNA controller/renderer, without using MC for playback.
(The script log do not show any termination of suspended processes when Media Server is running "standalone").

terrym@tassie · « **Reply #81 on:** October 22, 2017, 06:00:00 pm »

Quote from: cfrab on October 22, 2017, 04:05:53 pm

Unfortunately, now I found the same issue when using Media Server (run on win10 startup); the w10 start menu become unresponsive after a while when controlling playback from Media Server with Gizmo (android) or other DLNA controller/renderer, without using MC for playback.
(The script log do not show any termination of suspended processes when Media Server is running "standalone").

Well, that's a new one.
I run one of my systems extensively as a Media Server and I have never encountered an issue with the Start Menu when MC is NOT playing locally but then I don't use Gizmo to control playback a lot (but have done in the past without any issue). The script in it's current form (and V2) would not detect this as a situation where it needed to terminate processes.
Is it an intermittent random occurrence or does it follow a defined pattern like local playback, eg n minutes of served playback = Start Menu failure?
Also have I understood your post correctly, playback is not occurring in any local zone but is on a remote client and Media Server is just serving via the network?

amsco15 · « **Reply #82 on:** October 31, 2017, 08:14:20 am »

Been running the Fall Creator's Edition for a while now, still no problem with the start menu... There is a very slight delay after running MC and selecting start, search or action center but they all work regardless of the length of the MC listening session. Getting optimistic that this problem has been resolved.

Awesome Donkey · « **Reply #83 on:** October 31, 2017, 08:44:55 am »

It depends. It's potentially "solved" for some, and not others. For example, I still get Start Menu "death" after two hours of continuous playback of music.

Terry's been going down some interesting rabbit holes while looking into this and the Fall Creators Update, which I'm sure he'll post about once he's done with his testing.

terrym@tassie · « **Reply #84 on:** November 03, 2017, 01:04:14 am »

Quote from: Awesome Donkey on October 31, 2017, 08:44:55 am

It depends. It's potentially "solved" for some, and not others. For example, I still get Start Menu "death" after two hours of continuous playback of music.

Terry's been going down some interesting rabbit holes while looking into this and the Fall Creators Update, which I'm sure he'll post about once he's done with his testing.

Finished looking down the rabbit holes and completed update of w10spk to version 2. Please see this post: https://yabb.jriver.com/interact/index.php/topic,113034.0.html

Locking this thread now.

INTERACT FORUM

Author Topic: Windows 10 Start Menu and Modern Apps 'problem' - superseded (Read 28329 times)