Forum Discussion
Room System, version 4.4.25.0 does not start
My support case has not shown anything yet 😞
But from here you can see that this seems to be known issue at Microsoft:
Has anyone had any result at recovery?
We have 30 machines and 1/3 have the fault of displaying the new Teams logo and then going blank.
Have tried
https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/teams-rooms-app-wont-start-after-update
and
https://docs.microsoft.com/en-us/microsoftteams/rooms/recovery-tool
but still the issue persists. Attempting a Full reset of Windows now.
- Petri-XJul 27, 2020Bronze Contributor
As you can see: Room System Release notes there has been lot of improvements after disaster version 4.4.25.0.
Highly recommend to test a newer versions now.
- EddieSDGJul 21, 2020Copper Contributor
Mikegnz 2 of our 3 problem Logitech Smartdocks were 'fixed' by rebuilding with W10 Enterprise using these instructions https://docs.microsoft.com/en-us/microsoftteams/rooms/console
Once rebuilt they have behave normally & auto-updated to 4.4.63 without incident. Apparently 4.4.63 includes some fixes for some of the failure scenarios outlined above.
I now have an activation issue with my OEM license key not being accepted after the rebuild, but that's a licensing issue not an MTR issue.
As for the remaining device still on W10 Pro, it's in a remote office so until I can rebuild it I have disabled the scheduled task(s) that updates / reboots the device on a nightly basis:
get-scheduledtask -taskname NightlyReboot | Disable-Scheduledtask
get-scheduledtask -taskname ScanForUpdatesAsUser | Disable-ScheduledTask
get-scheduledtask -taskname ScanForUpdates | Disable-ScheduledTaskOf course, this means that the device is not updating automatically, so on a regular basis (weekly/fortnightly) I re-enable the scheduled tasks and allow it to update/restart overnight:
get-scheduledtask -taskname NightlyReboot | Enable-Scheduledtask
get-scheduledtask -taskname ScanForUpdatesAsUser |Enable-ScheduledTask
get-scheduledtask -taskname ScanForUpdates | Enable-ScheduledTaskBecause our issue is an OS issue, not a program issue we can start the Teams App manually from the Start Menu the next morning.
I haven't tested if all 3 scheduled tasks need to be disabled - it's probably just the NightlyReboot Task.
- evanwongJun 10, 2020Copper Contributor
Hello Mika, that's indeed bad experience. I yet have the honor to own the Flex image usb, I know we also have that at local Crestron office, but they're not releasing it to clients (or just me).
Anyway, here's something more interesting with our Flex, I went into this Microsoft post that mentions exactly how to manually update Teams Room, so I was all over the moon and couldn't wait to try it (because it's easier than wiping the whole thing clean then reinstall everything right?) The instructions and a few experience shared online, indicated that we should use the install APPX command, and not the update command, because that won't work, so I did, install the APPX 4.4.41, trying to force the update, offline, and it did go thru, and I restarted the machine a couple of times, following instructions.
And now, I end up with TWO Teams Room Apps installed on the Flex, the old version remains, and Flex writes its version 4.3.xx on the setting page; but when I log in to "Skype", the new version starts, 4.4.41.... wow! Then it went into black screen and stays there for as long as the sun (not auto logging out this time).
Now I scratch my head and blame myself for going on the adventure, cheers!
Ev.
- Mika SeppänenJun 10, 2020Copper Contributor
5 Crestron Flex rooms fixed, 1 Crestron RL2 room not 100% working but...
None of easy and quick fixes didn't help us, so here was our solution.
All divices restored from factory image, got it from Crestron, Flex images were not current version images, but still working ones. Crestron investigates why images were not correct, but we have no more time to wait for them. We got also latest firmware setup for Flex.
1. System flashed from USB -stick, Win10 -version and Teams version were old and not working ones
2. After flashing, use language and region US, then set Teams credentials etc.
3. When system was 'ready' Teams too old for login, don't look at that...
4. go to settings->windows settings
5. login as admin and install latest Flex firmware from USB -stick.
6. look that windows store installs all updates, for some reason Crestron asked to do this...
7. if any other windows settings (timezone if needed, IP if needed), set them BUT DO NOT GO TO WINDOWS UPDATE! Patently EVER.
8. Reboot system
9. Wait for tomorrow, and maybe one night after that. 1. nothing works, then Teams updates to latest version, and night updates windows.
- I tested with one Flex, change of Windows language and time format doesn't work in Teams 4.4.41.0 as earlier versions did.
- Our systems are now Windows 10 1903 and 1909!(how is that even possible?) Both are fine with Teams 4.4.41.0, at least now.
- One thing came out very clear, with Teams Rooms Systems, you may not go to Windows Update. If you go, you may get unwanted updates. And as Crestron debug our system, there was something wrong in Microsoft store and Teams packages. No idea what...
But, now we can use them, with no trust of them, and no trust for TRS development at all.
This was 3. time we got wrong updates in our systems.
TRS license is affordable, but if quality is this then...
- jepeltonJun 10, 2020Copper Contributor
I finally got it working again.
First of all i tried the teams recovery tool and it said that my windows version isnt ok. Then i upgraded windows with update tool to the latest version and of course this didnt work. So i made big mistake.
thanks to HP slices recovery partition, i managed to factory reset the whole machine using HP recovery tool from bios and everything works again. Lets hope future updates wont crash the system again.
- evanwongJun 09, 2020Copper Contributor
Hello Mike,
Yeh that was a version issue (I think Crestron Flex is with Enterprise edition?) Anyway I uninstalled 1909 update, and as soon as OS version downgraded to 1903, the recovery tool worked.
And that with the "reset" option cured the "Teams app failed to launch" error for me.
Now it only left me wonder did the recovery tool bring my Teams app up to 4.4.41 (as indicated in the tool's name), or the unit just some how got updated overnight...
- jepeltonJun 08, 2020Copper ContributorHello,
getting also same error message today, Tried to update to latest may build but still getting error. - evanwongJun 07, 2020Copper Contributor
Went thru all steps mentioned here:
https://support.microsoft.com/en-us/help/4565998/teams-rooms-application-does-not-start-after-update
Tried repair with the RecoveryTool, didn't work;
And the reset option gave me this error:
"The current Windows Version 10.0.18363.0 is not supported"
Machines: Crestron Flex
- Petri-XJun 05, 2020Bronze Contributor
Currently I have all devices with 4.4.41.0 version. The best what I could give is, do the reset so that you delete the room system folder and packages. And then do the repair, but with older version (4.4.35.0) if you have it.
But as told earlier, Microsoft has agreed about the issue and seems to be working with it. Perhaps the next version is giving help for us.