Jilas671

@jason thanks for coming back with a response on this and sharing a detailed response it's much appreciated. I'll drop a Pm over in a bit on just some thoughts in case they help. Again thanks for everything you and the team are doing, it's not easy when there are so many moving parts.

I note the test version we had lost the update channel, so had to go back to a earlier release and update and have 0.9.966 beta now installed. With the service re-enabled. Fire it up first time, it didn't work was a bit odd (may have been me). Did create the remote, skipped passed the add device stuff so I could just do a restore (an option for this at the start might be good, especially as it seems you can detect if the remote is new or has been updated). So tried a second time, this time it did bring up the pop up after the remote was detected and sync was tried. Get the previous windows permissions error then your new pop up with the download link, used that installed the "fix". Checked the services it does disable it correctly - some of the messages are kinda worrying, (I think deleting usb devices .. was a fun one to see). When complete return to the app. Remote is picked up, and could sync. Swapped remotes, picked up the second one ok, (as a fresh install) tried to skip past the setup which locked the app up, needed a restart to clear that. Came back to the blank second remote, imported the config ok. Remote connects (doesn't offer a sync this time). Swap them over again the app swaps to the other remote correctly. So looks like this is all working to fix the usb/logitech/steam issue. Thanks for getting it included and working. Can I dare ask if there will be an update or a roadmap for the remote and things we can expect (no dates, or order) just so we can see what's hopefully coming at some point. Just my remotes are still in their boxes waiting for some key changes and would be at least nice to know these are still planned and will appear at some point (time etc permitting). Happy to post or message you a list of what I'm hoping for and you can confirm yes/maybe/no if easier.

No problem, just good timing on when you posted. I guess you expected the new app, to block the skip software from connecting, in a similar way that the logitech service does. And I guess that proves you can grab sole control over the remote when they are plugged in without asking for extra permissions. Very happy to test any versions as you need (timezones permitting of course will depend on the speed of the answer). PS those commands I mentioned are one of the worst case options, next to doing it manually in the service panel, they just need sticking in a batch file (or run from a command prompt) as long as it has admin privileges - it will just stop and then block the service.

So quick test for you. Enabled the service checked the Skip app, fails. As expected. Run this app, get a small window, with disconnected, (percent bar 0% and load file). Plug in the remote Disconnected changes to Connected. Tried this with the service on Auto and Manual, - but running both times the same. The service state does not change and is running all the time. Just to confirm load up the Skip App on its own, and that can't connect. Out of insanity. with the service disabled. this app running, then start the skip app, that throws the warning message again and never connects... until I close this app and then Skip app connects to the remote without needing to be reloaded. So looks like you are onto something. Hope the feedback helps.

Sorry timezones and such make answering slow at times.. Happy to test anything you have, but to be honest we have a solution, just add that to the faq. Or give them a batch file that if run as admin stops the service and then disables it. A quick test these are the lines people would need to run in a admin command prompt. net stop logi_lamparray_service sc config logi_lamparray_service start= disabled And sc query logi_lamparray_service checks if its running. Still waking up, but could be thrown into a batch file, or I assume you can call this within an app. As said I think you have spent too much of your precious time fixing windows issues, to do much more than have a faq somewhere. But if you have something happy to test and feedback.

@jason Thanks for looking at this, and thanks to @Wesley for providing the platform to get to this stage. Can confirm the craziness I had all fixed by stopping the service. No pop up asking for permissions each time which I guess is the big red flag for the future if people have problems. Why these remotes are being picked up as a possible logitech device is strange for sure, I just hope this confirmation and thanks, helps in some small degree. And I do hope you can take a moment to relax and know people are thankful for your support.

And registry files. I do hope this helps, as I'm sure you want to progress on the features than this windows bug fixing. Registry.zip

That was the version I was using, and not sure what is going on as nothing connects correctly and will grab the logs, but I think starting a fresh and then take it one step at a time is the way to go. So clean install, sitting at the connect your flirc remote.. connect the remote... I get the Do you want to allow this app from unknown publisher to make changes, and the app is SkipDevice RestrictionBroker.exe (as I type this it prompts again). click yes....and nothing. Close the app and get another prompt to make changes (its as if these changes are just not getting processed/allowed) On second attempt nothing, until I close the app then get prompted again. The continue button never appears. (tried both remotes) So using I'll do this later. I create a remote (Bottom left, not connected, Bottom middle,Gray-connecting...- remoting the remote changes this to offline) (At this point, its so annoying to need to create activities. vs being just able to import a backup, also why does it default to looking at Pictures folder) Import previous remote setup (fine), export it (fine - still working with Live drive - thanks). So quit (get prompted for permissions again). Remote the remote, start the app, connect the remote... no prompt, not connection (stuck at connecting), when I close the app get the prompt up. Below are the logs (next post will be the registry) Skip Logs and Registry - 5-5-24.zip

As I said earlier, happy to test this out, but for some reason never got a notification that the thread had updates (I've checked the follow topic again button again just in case I missed it last time). So I tried both apps listed and with the last version a single successful connection.... but since then nothing (maybe swapping remotes was an issue). Often on closing the app I will get prompted about giving permissions vs when a remote is connected, again that's very random and maybe I've missed a key step with this new version. I'm also your worst nightmare, Steam and Logitech user all on Windows 11. But if you want anything testing, let me know what and what order the steps should be in. Knowing windows, it's almost needing to reboot the pc for each test just to be sure nothing was left over from the last time the app was run. And a very clear step guide on what to do (or not to do).

That's the old way, it's now an option in the app. May well do the same thing.

I don't have the pc open, but from memory, if you look in the bottom right corner there is a menu 3dot , in there go into settings and you should have an option to enable the admin tab.

I don't know if this helps but feels related to the same issue. As I posted in Feb, since the last few version prior something changed and the software does not connect any more (yes steam is installed and this is windows 11). Just tried 0.9.965.7443, same thing. Things of note. If I start the application with the remote already attached I get a Windows UAC dialog asking to approve when the software loads, but then then it sits there connecting.... for ever.. If I remove it and connect the remote nothing, no prompt for UAC, no connection. If I go into the admin page in the app and use the select device and connect, the connection icon briefly tries, and then I get error 500 reported back. If the app is loaded and the remote (first time only) is connected, initially I never got a dialog, but after restarting the app after updating, and repeating the steps so I could to write this now it's working. Also if you don't agree or disagree to the UAC it does prompt again...sometimes. Swapping between the two remotes I have, makes no difference and doesn't change anything. I'm happy to help test any code, as its as equally frustrated as I backed this and the two remotes are still not in use, as waiting for other features to appear (naturally these are held up by this issue).

Currently, you have to name the remote, then if you skip the add activity then you should be able to import. It worked to the point of having the activities all present... just with the device not connecting I can't confirm if it would push to the remote, but everything looks and suggests it should. But I guess that's my point, it would be nice to be able to plug in a remote, and the app, checks if its factory fresh or has been used. If used then offers and extra options for a fresh install or import a configuration file (it would be amazingly useful if it could download from the remote the config as well, but experience with esp's would suggest that could be much harder that it sounds).

So I updated to the current beta on my Windows 11 pro machine, and tried to connect a remote, and just never connected. Long story short, looks like I have hit the same bug with SkipDeviceRestrictionBroker.exe and steam reported elsewhere. Which is odd as steam has always been around, and was fine the last time programmed them, so confused. I always tried to backup the remotes, so it was the 0.9.954 versions as that was the first time the livedrive issue was resolved (and it sill fixed). So I will look over the not detected post, and see if any of that helps me or I can add any additional info. Now having done some re-installs on Windows 11 to get to this point, a couple of minor observations. Firstly it would be useful if on initial setup, the app, could check if the remote is blank or has a config (or just asks). So you get a choice if you want to import an exported config or to start a fresh. Also when you import remote settings. Two oddities here. 1) on a fresh install, it defaults to pictures not documents. 2) when you import a remote, all good it appears, but if you have multiple remotes, you cannot import the second one, without connecting it to the pc. Would be good if when you import a configuration that it asks if you want to add it to this remote, or create a new remote. These remotes only come out for testing updates (as still not family friendly for me), on the off chance some of the features in the pending list have been applied, like how activity switching is done, and additional code space in the colour/dial menu and the most important now is the play/pause where its a different key with some devices.

@jason Hadn't heard anything, so today I randomly unpacked the remotes from their boxes and tried the current beta (0.9.954), and export works, it does what it should, produces a have a file for the remote, and the app doesn't crash anymore. Hopefully this was a planned changed, but seeing things have been quite here, I don't for sure if this is intentional fix or accidental, or even something MS fixed! But providing feedback, just so you are aware something has changed for the better.