I got a bug that seems to prevent me from opening any file. I updated to the latest version (I think I was on v2.6.0 and had just updated to v2.6.3).

I couldn't open files from the File>Open menu. I couldn't open files from the recently opened menu. I couldn't drag files in from Windows Explorer. I tried resetting my settings to factory defaults but still nothing happened.

When I dragged stuff in, sometimes the mouse cursor would turn to the "loading" circle, but then nothing would happen. When I tried dragging in 3 files at once, I got the "would you like to merge your files" popup, and if I said "yes" nothing would happen.

I pulled up Task Manager and it didn't seem like LogViewPlus was using any reasources, no RAM and no CPU, so it wasn't busy trying to parse my files...

I also tried re-opening LogViewPlus as an admin, but that didn't change anything.

There seems to be some files I can open. Specifically, I was able to open recently used logs in a sub-folder inside my Downloads folder. But the vast majority of files I couldn't open no matter where they were (Downloads, Downloads/randomFolder, Desktop, Desktop/randomFolder)

I tried reinstalling version 2.6.3 and still had the issue. I tried turning off DirectX just to see if it would help but it didn't change anything.
My last step was uninstalling 2.6.3 and downloading and installing 2.6.0, and that worked!

So I'm up and running now, but if I had to guess there might be a bug in the new release? I know one of my coworkers mentioned they had an issue like this but I hadn't had time to talk to them to see what was going on, but perhaps they're on the latest version and had the same problem?

If it would help, I can make a little screen recording simulation. Or if there are log files I can grab for you to see what's going on, let me know. I am quite sure this isn't a problem with my parsers, since I tried multiple different file types without success.

I'm seeing this issue as well.  My machine is Windows 10 Enterprise 21H2.  Files are all network shares.  I usually don't have a need to open anything locally, so everything I tried wasn't working.  I can try to find out the OS these file shares are running if it would help.
I just tried a couple of local files.  I was able to open a log file for an application inside my appData\Local folder and a file inside my Downloads folder.  It failed to open a log file for a program inside C:\Program Files.  I cannot open this file when running LogViewPlus as admin either.

For now, I'll downgrade to 2.6.0, but I'm willing to help test if needed.

Thanks Chris - that's a big help!

I tested in my local Program Files directory and I believe I was able to recreate the issue.  Just prior to the 2.6.1 release we modified one of our URI validation steps.  The new version is URI escaping, so 'Program Files' becomes 'Program%20Files' which doesn't exist.  LogViewPlus does not consider this an error because sometimes log files do not exist for one reason or another so the application fails silently (these types of decisions need better visibility).

This is likely to be the root of the problem that everyone is experiencing on this thread.  If you are having issues with a path that does not contain spaces, or other characters that need to be URI escaped, then please let me know.

As this is a critical issue we will try and get a release out as soon as possible.  I will look into creating a BETA release tomorrow.

Thanks for your help everyone! 

Toby