I'm happy to keep chipping away at it. Current hypothesis is that there's spaces in the command line and the diagnostics in the version I uploaded yesterday should show me what's up because I put angle brackets in there. There's a whitespace eater at the start of the command line, I didn't put one at the end of it because I've never had to in the past but it's conceivable you somehow got spaces in there so I added that in version 5.4 -- although in testing it I notice I can't actually add space at the end of a command line as the explorer removes it so less hope for that one so I've dialed the diags up a bit more. If that's not it I'll dial the diagnostics up yet another level to try and show me what's up. Yeah, the move option was there in win10 for a little while, you had to right click and then right click again but you're right, it's gone now. Just Googled that as if you move a window off the screen that's about the only way to get it back and I see that you now have to shift-right-click the icon to expose the Move option. Of course a Launcher shortcut is going to be a superior experience if you always want to move the window to the same location. I use it to move my email client from the small unreadable monitor to my big screen and have another shortcut to move it back once I'm done actually reading stuff and merely want to monitor it again.
Thanks for feedback, I have since recycled computer multiple times and I believe some more updates came out and now I'm having no more issues with the remote. Go figure it works now.
I just uploaded another version of 5.4 in between edits of my post, sorry about that, thought you only logged on in the early morning (my time). Fire up the one that's on the page right now and paste me in a few lines of debug view's data on an attempt to reposition a window.
got the new ver, shouldnt it be named 5.4.1 or something?? I can be on at anytime. I run Dbgview, open WMC, then minimise it, then unminimise it, then save Dbgview log file with all default settings. Spoiler 00000001 0.00000000 [4420] lookforexecuting <C:\Windows\ehome\ehshell.exe> 00000002 0.00123114 [4420] lookforexecuting considering <C:\Windows\System32\sihost.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000003 0.00128556 [4420] lookforexecuting considering <C:\Windows\explorer.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000004 0.00133969 [4420] lookforexecuting considering <C:\Windows\System32\RuntimeBroker.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000005 0.00139176 [4420] lookforexecuting considering <C:\Windows\System32\svchost.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000006 0.00144179 [4420] lookforexecuting considering <C:\Windows\System32\taskhostw.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000007 0.00149182 [4420] lookforexecuting considering <C:\Windows\System32\igfxEM.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000008 0.00154068 [4420] lookforexecuting considering <C:\Windows\System32\igfxHK.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000009 0.00159305 [4420] lookforexecuting considering <C:\Windows\System32\igfxTray.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000010 0.00164689 [4420] lookforexecuting considering <C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000011 0.00169779 [4420] lookforexecuting considering <C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000012 0.00174753 [4420] lookforexecuting considering <C:\Program Files (x86)\TeamViewer\TeamViewer.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000013 0.00179815 [4420] lookforexecuting considering <C:\Windows\System32\SettingSyncHost.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000014 0.00184759 [4420] lookforexecuting considering <C:\Program Files\Windows Defender\MSASCuiL.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000015 0.00189645 [4420] lookforexecuting considering <C:\Program Files (x86)\Samsung\RAPID\CacheFilter\SamsungRapidApp.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000016 0.00194472 [4420] lookforexecuting considering <C:\Program Files (x86)\ServerWMC\ServerWMC.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000017 0.00199475 [4420] lookforexecuting considering <C:\Program Files (x86)\Garmin\Express Tray\ExpressTray.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000018 0.00204303 [4420] lookforexecuting considering <C:\Program Files\Nefarius Software Solutions\ScpToolkit\ScpTrayApp.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000019 0.00209189 [4420] lookforexecuting considering <C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000020 0.00215011 [4420] lookforexecuting considering <C:\Users\Authorised User\Downloads\launcher\Dbgview.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000021 0.00219751 [4420] lookforexecuting considering <C:\Users\Authorised User\Downloads\launcher\launcher.exe> vs. <C:\Windows\ehome\ehshell.exe> 00000022 0.48363778 [4812] onecore\base\appmodel\resourcepolicy\gameconfigstore\client\gameconfigstoreclient.cpp(104)\resourcepolicyclient.dll!00007FFCE9A4976C: (caller: 00007FFCC71889B7) LogHr(37) tid(1030) 80070490 Element not found. 00000023 1.04955137 [4420] c0506 1936 0 1119 0 2166384 window candidate 16cf0000 20040900 00000024 1.04958272 [4420] 15068c 136 0 39 0 5304 window candidate 04c00000 00000100 00000025 1.04961467 [4420] 8073c 0 0 0 0 0 window candidate 84000000 00000000 00000026 1.04964149 [4420] 1d03e0 1924 -8 1060 -32 2109744 window candidate 06c10000 00050100 00000027 1.04967105 [4420] 903e4 136 0 39 0 5304 window candidate 04c00000 00000100 00000028 1.04969656 [4420] 704c8 1 0 1 0 1 window candidate 84000000 00000000 00000029 1.04979277 [4420] 9055c 0 0 0 0 0 window candidate 8c000000 00000000 00000030 1.05033195 [4420] better candidate c0506 move didn't fail 00000031 5.04993105 [4812] shell\explorer\taskband2\taskband2.cpp(4148)\Explorer.EXE!00007FF7E81E877A: (caller: 00007FFCEBE78443) ReturnHr(215) tid(1318) 80004005 Unspecified error
It's possible, I guess, but not having it happen when I open YouTube in Edge makes me think that it is something else.
If I pump out mods to something I released in the last few minutes I won't change the version number unless it has serious ramifications, here it's the presence or absence of additional diagnostics and I can see whether they're present or not (they are). I just see the initial launch in those diags, I don't see the relaunch once WMC has been minimized and maximized. In any event it tells me as much as I needed to know from that set of diagnostics (assuming relaunching still fails to find the window of course). No spaces in the name and no corruption of the name by the time it actually examines the eshell process. Have to think about that one as about all I can think of are unprintable characters related character set issues in the name and that's going to generate a lot of debug spew. Still thinking about what to do next. OK, so stricmp() must be failing when it's passed strings from process file names even when printf() prints the names identically (even though we're using 8 bit characters), betting it's something to do with locality settings and soo we'll use _stricmp_l() that's some wonder MS routine and we'll see if that makes a difference in version 5.4.1 that's now up there. If it still fails to find the window (because it couldn't find the process) please post the DebugView spew and I'll see if I have to tweak locality settings (I use LC_ALL this time).
tried version 5.4.1 , still the same thing, am i doing anything wrong? i reuse my shortcuts made originally, i have also tried making new shortcuts, i replace the newer files in the same directory from your newer versions?? "right click it and click the "Windows Media Center" link." works though... Spoiler 00000001 0.00000000 [1808] lookforexecuting <c:\windows\ehome\ehshell.exe> 28 00000002 0.00154975 [1808] lookforexecuting considering <C:\Windows\System32\sihost.exe> 30 00000003 0.00160973 [1808] lookforexecuting considering <C:\Windows\System32\svchost.exe> 31 00000004 0.00166532 [1808] lookforexecuting considering <C:\Windows\System32\taskhostw.exe> 33 00000005 0.00172032 [1808] lookforexecuting considering <C:\Windows\explorer.exe> 23 00000006 0.00177182 [1808] lookforexecuting considering <C:\Windows\System32\RuntimeBroker.exe> 37 00000007 0.00182214 [1808] lookforexecuting considering <C:\Windows\System32\igfxEM.exe> 30 00000008 0.00187275 [1808] lookforexecuting considering <C:\Windows\System32\igfxHK.exe> 30 00000009 0.00192307 [1808] lookforexecuting considering <C:\Windows\System32\igfxTray.exe> 32 00000010 0.00197486 [1808] lookforexecuting considering <C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe> 79 00000011 0.00202723 [1808] lookforexecuting considering <C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe> 74 00000012 0.00208370 [1808] lookforexecuting considering <C:\Program Files (x86)\TeamViewer\TeamViewer.exe> 48 00000013 0.00213753 [1808] lookforexecuting considering <C:\Windows\System32\SettingSyncHost.exe> 39 00000014 0.00218727 [1808] lookforexecuting considering <C:\Program Files\Windows Defender\MSASCuiL.exe> 46 00000015 0.00224022 [1808] lookforexecuting considering <C:\Program Files (x86)\Samsung\RAPID\CacheFilter\SamsungRapidApp.exe> 68 00000016 0.00228996 [1808] lookforexecuting considering <C:\Program Files (x86)\ServerWMC\ServerWMC.exe> 46 00000017 0.00233940 [1808] lookforexecuting considering <C:\Program Files (x86)\Garmin\Express Tray\ExpressTray.exe> 58 00000018 0.00239002 [1808] lookforexecuting considering <C:\Program Files\Nefarius Software Solutions\ScpToolkit\ScpTrayApp.exe> 70 00000019 0.00243917 [1808] lookforexecuting considering <C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe> 64 00000020 0.00250032 [1808] lookforexecuting considering <C:\Windows\ehome\ehtray.exe> 27 00000021 0.00255210 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000022 0.00260330 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000023 0.00265304 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000024 0.00270278 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000025 0.00275486 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000026 0.00280401 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000027 0.00285287 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000028 0.00290202 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000029 0.00295117 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000030 0.00300237 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000031 0.00305152 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000032 0.00310185 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000033 0.00315071 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000034 0.00319957 [1808] lookforexecuting considering <C:\Program Files (x86)\Google\Chrome\Application\chrome.exe> 59 00000035 0.00325077 [1808] lookforexecuting considering <C:\Windows\System32\backgroundTaskHost.exe> 42 00000036 0.00330314 [1808] lookforexecuting considering <C:\Users\Authorised User\Downloads\launcher\Dbgview.exe> 55 00000037 0.00335112 [1808] lookforexecuting considering <C:\Users\Authorised User\Downloads\launcher\launcher.exe> 56 00000038 0.49782619 [4868] onecore\base\appmodel\resourcepolicy\gameconfigstore\client\gameconfigstoreclient.cpp(104)\resourcepolicyclient.dll!00007FFC2D8A976C: (caller: 00007FFC0BAA89B7) LogHr(31) tid(25a4) 80070490 Element not found. 00000039 1.05037558 [1808] 1202ea 1936 0 1119 0 2166384 window candidate 16cf0000 20040900 00000040 1.05040896 [1808] 505e8 136 0 39 0 5304 window candidate 04c00000 00000100 00000041 1.05044055 [1808] 903d0 0 0 0 0 0 window candidate 84000000 00000000 00000042 1.05047250 [1808] 507cc 1924 -8 1060 -32 2109744 window candidate 06c10000 00050100 00000043 1.05050409 [1808] 60466 136 0 39 0 5304 window candidate 04c00000 00000100 00000044 1.05053127 [1808] 18015e 1 0 1 0 1 window candidate 84000000 00000000 00000045 1.05064476 [1808] 7074e 0 0 0 0 0 window candidate 8c000000 00000000 00000046 1.05122256 [1808] better candidate 1202ea move didn't fail 00000047 37.21466827 [4868] shell\explorer\taskband2\taskband2.cpp(4148)\Explorer.EXE!00007FF6FFCC877A: (caller: 00007FFC32118443) ReturnHr(220) tid(1368) 80004005 Unspecified error
It looks like you're using it properly, however I need to see the debug spew from a re-launch attempt, that is one where you've minimized WMC and now want to reposition it on the screen -- assuming that continues to display the couldn't find window dialog of course...
I did minimise and restore MCE in my previous post...? i just restored it in this log Spoiler 00000001 0.00000000 [8960] avcore\npsm\localprovider\baseprovider\lib\baseprovider.cpp(604)\NPSMDesktopProvider.dll!00007FFC01862140: (caller: 00007FFC018626E5) ReturnHr(36) tid(1c70) 80070490 Element not found. 00000002 0.06961425 [8960] shell\explorer\taskband2\taskband2.cpp(4148)\Explorer.EXE!00007FF6FFCC877A: (caller: 00007FFC32118443) ReturnHr(153) tid(280) 80004005 Unspecified error 00000003 1.86067641 [8960] avcore\npsm\localprovider\baseprovider\lib\baseprovider.cpp(604)\NPSMDesktopProvider.dll!00007FFC01862140: (caller: 00007FFC018626E5) ReturnHr(37) tid(1c70) 80070490 Element not found.
Yeah, it's not the minimizing of WMC that we're interested in seeing the diagnostics from, its the subsequent use of Launcher to reposition the window that fails with the message about not finding a window. If that's no longer the case and you're not getting messages you're good, job's done, the new string comparison routine was able to match the processes names. I'll probably release another version that uses a wider dialog given how large screens are these days (the old dialog was designed in about 2002 when things were quite a bit smaller than they are now).
Yeah i know that lol, just thought id give you a cleaner log The only time i get the failure window is if i have WMC running and then double click on the WMC desktop shortcut. You are nearly there, being able to restore WMC by clicking on it in the taskbar whilst its running and minimised, to get it to restore in the correct place on the screen would be great.
Yeah, that's something I've thought about every now and then. I'll do a bit of investigative work to see what a minimized window looks like, from memory a minimized window is just moved way to hell and back off the screen some place, will be interesting to have a peek and see. Ok, there's 6.0 that maximizes windows if they're minimized. Seems to do a bit of a number on Thunderbird's title bar but I've already got funky CSS in there to color it's title bar so I'm not worried, WMC functions we we'd expect.
Hope you get there, your Launcher is for me the easiest option, nochrome doesnt have a taskbar icon and then it does after minimising it and then its a PITA to move. Moving the window by hand takes a steady hand and always leaves one pixel at the top and one pixel at the bottom.
Yeah, it's not having the window "activated", whatever the hell that means. Noticed that if I clicked the restore icon in the system menu of the app the title bar went back to normal. If I send the minimized applications SW_RESTORE instead of SW_MAXIMIZE with Launcher things look better so try 6.0.1 that's up there right now.
SOOOOO close if i click on the WMC taskbar icon it opens filling the screen fully, as it always has done. if i minimise WMC then maximise it, it then comes back withe the border showing and not in the same position as when it was first opened, like before. If i manually move the window, leaving that annoying pixel at the top, and then minimise and maximise it, it goes back to just having the one pixel at the top, which it didnt do before, before it would go back to showing the border and in the wrong position. However, this all gets reset if WMC is closed.... Hope that makes sense.
Yeah, Launcher isn't going to change WMC's maximization from minimized state, that's all completely out of it's control. All Launcher is going to do it is if the WMC Launcher shortcut is run while WMC is minimized it'll maximize WMC and then move it to the location it should be (after a half second). You can access that functionality by pinning the WMC Launcher shortcut to the taskbar instead of the pure WMC one and win10's taskbar will behave like that's the WMC window (somehow it makes the right decision). If you then want to re-launch WMC while it's minimized you have to right click that taskbar icon and select the "Windows Media Center" option which will run Launcher, it'll see the WMC process is active and it'll see that it's minimized and maximize it and then move it. Just clicking on the icon will do the usual Windows maximization and WMC will make sure it's title bar isn't right off the screen.