Isn't it funny that after 1h30 of scanning I'm on 0%
I hope it's only an UI issue and, indeed, the scanning is running in background
The scanning should be running.
There's no way to tell at the moment other than looking at the CPU usage of the process.
The scan stuck on 0% is a known issue (rootkit scan is actually running) and will be fixed in the future...
That's why I've been nagging them to bring back last file scanned and the amount of files/data currently being scanned and the speed of how fast the scan is going in MB/s. If users see stats moving, they know things are working and just going slow but if you have no stats, you just think it's stuck.