If you're the administrator of your workstation, I'd check to see if changing out/updating your audio/video/Bluetooth/network/etc drivers helps at all. Other than that, some other app may be conflicting or there could be a memory issue. It's not likely that you'll find an error, because if it's a temporary not-responding, it's unlikely the app even realizes there was an issue. All you can really do is try to eliminate variables until you find the issue. See if running it in safe mode with nothing else running makes it run more smoothly, or if it's still getting hung up.
Hi Anthony,
I totally uninstalled the bluetooth stack after updating it and it not helping.
I have the latest Intel video / IDP audio / HP drivers as well.
I didn't note this above, but when this happened yesterday, i realized that the lync engine seems to be ok and that it's the UI that's dying. I went through a whole call with the application not responding but being able to hear/talk.
You're correct about nothing being in the logs (that i can recognize)
I'll try the safe mode.
Thanks
Hi alex1alex,
If the issue still persists, you may try signing in with another Windows account and then check if it works.
Best regards,
Eric
Hi Eric,
What's the thought process behind this? They my account on the lync server is corrupted?
(Also, I'd have to have a co-worker log into my laptop...no?)
Thanks,
Alex
Hi alex1alex,
Not the AD account.
I mean that you may sign in with the local administrator account , or if you have administrator privileges you can create a new local account.
Maybe there's something wrong with the Windows profile.
Best regards,
Eric
Hi alex1alex,
Im writing to follow up on this thread. Do you have any updates on this issue? Please post back at your convenience.
Best regards,
Eric
Nothing really interesting.
In addition to the above, today I ran Office repair.....will see if it happens again...
Hi alex1alex,
Any progress ?
Did the repair fix this problem ?
Best regards,
Eric
Hi Eric,
Yeah, the problem seems to be gone.
Unfortunately, I don't really know why.
Thanks everyone,
Alex
- Marked as answer by Eric_YangKMicrosoft contingent staff, Moderator 6 hours 20 minutes ago
Hi Eric,
Yeah, the problem seems to be gone.
Unfortunately, I don't really know why.
Thanks everyone,
Alex
- Marked as answer by Eric_YangKMicrosoft contingent staff, Moderator Tuesday, September 08, 2015 1:01 AM
Hi Eric,
Yeah, the problem seems to be gone.
Unfortunately, I don't really know why.
Thanks everyone,
Alex
- Marked as answer by Eric_YangKMicrosoft contingent staff, Moderator Tuesday, September 08, 2015 1:01 AM