Windows 7 if I close my laptop with L6 still open, when I come back into the program it no longer syncs and has the red exclamation mark until I completely close Logos and reopen.
This is still occurring, only replying because it got lost in the shuffle.
Please post your logs so we can diagnose this issue further.
Alright, I'll do that when I get home this evening.
Here are the logs, last night was the last time it happened.1362.Logos Log Files.zip
Is this still an issue for you?
I had a similar issue on my Surface Pro 3 when Hyper V was enabled. Turning off Hyper V resolved the issue. MS has since fixed that issue with an update.
Yes it is still an issue, what is Hyper V and how would I check to see if it is enabled?
Hyper V allows users to run Virtual Machines.
This is the article I followed which resolved my issue:
http://answers.microsoft.com/en-us/surface/wiki/surfpro3-surfnetwork/work-around-for-surface-pro-3-issue-where/bd7c8bde-439b-45d6-8d9d-2776913e45e9
This is the same in Windows 7?
[:|] I doubt it. The problem with the surface was certainly a Windows 8/8.1 issue. I suspect the steps to turn it off if it's on would be the same but it's likely not on and will (even more likely) not change anything to turn it off.
Back to the drawing board on our end. I just thought I'd mention my personal experience in case it helps.
This is the same in Windows 7? I doubt it. The problem with the surface was certainly a Windows 8/8.1 issue. I suspect the steps to turn it off if it's on would be the same but it's likely not on and will (even more likely) not change anything to turn it off. Back to the drawing board on our end. I just thought I'd mention my personal experience in case it helps.
I doubt it. The problem with the surface was certainly a Windows 8/8.1 issue. I suspect the steps to turn it off if it's on would be the same but it's likely not on and will (even more likely) not change anything to turn it off.
NO worries. Thanks for working on it. It is more of a nuisance than a problem. But it would be nice to figure it out. I know that I had hoped it wouldn't do it any longer after I completely wiped Windows 7 (for the other issue you know about) but it did it after that. So I think we can rule out Windows itself as the problem.
The logs are from 2014 so you have to permanently enable logging so it can capture the detailed events.