If you're already working locally, try these steps, then reach out to our Support Engineers if you are still seeing the issue. And be sure to let me know if you do decide to open a case so I can follow along. :)
It happened after we upgraded to windows 10. When I am at work and docked, it is working fine. But When I am at home it's showing this behavior. It is a fresh capture and I am saving to my desktop which is c drive.
Most probably it's a network issue (it works fine when it docked and connected to network via ethernet port) I'll check with our IT team.
3 Replies
Really strange, Surya. Thanks for including the screen capture. That's definitely not something we'd expect to see!
Is it possible you're working from a file that is stored on a network or flash drive? Those types of drives are notorious for causing issues with Replay files, so you'll want to make sure you're working from your local C: drive.
If you're already working locally, try these steps, then reach out to our Support Engineers if you are still seeing the issue. And be sure to let me know if you do decide to open a case so I can follow along. :)
It happened after we upgraded to windows 10. When I am at work and docked, it is working fine. But When I am at home it's showing this behavior. It is a fresh capture and I am saving to my desktop which is c drive.
Most probably it's a network issue (it works fine when it docked and connected to network via ethernet port) I'll check with our IT team.
Hi Surya,
Hm, that's interesting. Let me know what your IT team says, and we'll keep investigating if we need to!
This discussion is closed. You can start a new discussion or contact Articulate Support.