- Context menu
- User data profiles
- Credit Cards
- Spell Checker
- Common exceptions
- Application does not terminate
- Video does not play
- Cannot sign in to Google account
- User data is not stored
- Color scheme
- Startup failure
- Slow startup on Windows
- Unresponsive .NET Application
- Unexpected Chromium process termination
- Unexpected behavior
- Windows 7/8/8.1 end of support
If DotNetBrowser fails to start in your environment, perform the following actions:
- Make sure that your environment meets the system requirements.
- Configure your antivirus software to allow DotNetBrowser to run.
DotNetBrowser runs Chromium in a separate native process. Sometimes it fails to launch the native process due to the installed antivirus software or due to local security policy. Even though all DotNetBrowser executable files are signed with a valid and trusted signature, some antivirus software may still not allow running programs that are not in their whitelist.
If the actions above do not help, enable logging, reproduce the issue, and submit a ticket with the collected log messages.