Roastime not loading

Another attempt assuming McAfee causing the problem. Uninstalled RT3 and cleared the McAfee quarantine files. Reinstalled RT3 and watched the quarantine. RT3 opened fine on first attempt. Closed and tried to reopen again and this appeared in the quarantine file and says it is unable to restore.

I tried to exclude the Roastime files from McAffee but that didn’t work.

Same issue just happened to me. Please help. Thx

Please do not have both RT2 and RT3 installed at the same time, this can cause the white screen.
Regarding the anti virus could you try to disable real-time monitoring and check if it then works?

Hi Jacob,

I turned off McAffee’s real-time monitoring and it didn’t work. I deinstalled and reinstalled Roastime with it off and it still didn’t work.

Thanks,
John

RT2 has been removed and the white screen issue appears to have been resolved. But McAfee still causing issues with RT3. Deleting the shortcut path and unable to get McAfee to ignore the RT files.

Got the .exe files added to the excluded list. Will see if this helps resolve the issue.

Are there other anti-virus software that don’t cause this issue? Does Norton play better with RT?

I removed my trial McAffee software and installed AVG antivirus, still no luck after deinstall and reinstall.

That’s frustrating.

You might need to enable viewing of hidden files. In your file explorer find the view settings and enable hidden items.
After uninstalling all apps try deleting these folders:
C:\Users<YOUR USER NAME>\AppData\Local\RoasTime
C:\Users<YOUR USER NAME>\AppData\Roaming\RoasTime
C:\Users<YOUR USER NAME>\AppData\Roaming\roast-time

Then re-install RT3 only.

Update.

Removed RT2.5.7, which I had left on after RT upgrade, and white screen issue has stopped.

Reinstalled RT3.1.8 and added the RoasTime.exe file to McAfee’s excluded file list as shown in the screen shot above. So far no issues with the icon going white and no error messages about the shortcut path not working.

Just got done roasting a batch of coffee with no issues. RT and the Bullet both worked perfectly.

Will update again if any issues do occur.

Did that and it worked. Did two 350 g roasts and still working.

Grazia,
John

Glad you guys got it working - yeah, as Jacob mentioned, the 2 aren’t meant to be running side by side since they share a directory structure. So each time you open the other one, it causes a data corruption issue.

I will see if I can’t figure out why Mcafee is flagging us.

Thanks!

@mcaillio it’s not just Mcafee, but Norton as well.

1 Like

Not working again.

McAfee keeps removing the excluded files.

Seemed like RT 3.1.8 worked ok. But when I did the update McAfee removed the excluded files because they were updated. Now RT won’t open at all. Icon still remains but nothing happens. And McAfee keeps removing the files each time after I add them to the excluded list.

Update Uninstalled RT3.1.9 again. Reinstalled 3.1.8 and skipped the update. Seemed to work fine before the update yesterday, so just going to stick with that for now.

I don’t have McAfee so difficult to help. I use windows defender and that seems to work ok.

Ok I am now having same problem but with Trend Micro anti virus software. Even when I click “Trust this Program” it just keeps repeating and nothing happens. Has only happened since RT software update.

Hey @Snidely_Whiplash - I see you can click on “file”. Does that show the path to the file? If so, can you send it over?

@mcaillio I reinstalled Trend Micro to bypass the issue and it works now. However I lost the history of files blocked. The file would have been the Aillio RoastTime update exe file, as it just blocked RT after doing the update

It might be interesting to verify which file Trend Micro Folder Shield is protecting. From the TM website:

Your Trend Micro security software can prevent ransomware from maliciously encrypting your files and holding them hostage until you pay the attacker. Folder Shield adds an extra layer of defense that limits access to files within the protected folder.

1 Like

Yeah, that is my thoughts exactly. Not sure what file we would be trying to access that it doesn’t like. If it pops up again, let me know the path.

Thanks!