Bilar Crais

That did the trick. BTW, before I knew you had a beta available, I had purchased a different product to fill in temporarily. From a company that Rhmynes with FarClock. Let me say that your product utterly destroys the competition.

I don't have a "local dump" subkey for "Windows Error Reporting", whereas the tutorial you've linked to shows it there by default. However, I can try to create it. By the way, this is what's happening as the result of the crashing in Windows Error Reporting/App log: Faulting application name: explorer.exe, version: 10.0.10166.0, time stamp: 0x55976770Faulting module name: painter_x64.dll, version: 1.0.0.4, time stamp: 0x54fc14dbException code: 0xc0000005Fault offset: 0x000000000000128bFaulting process id: 0x1344Faulting application start time: 0x01d0bc1d3a6f46dcFaulting application path: C:\Windows\explorer.exeFaulting module path: C:\Windows\System32\painter_x64.dllReport Id: 27cbbb8a-26ab-4ac7-85ac-4abc73d9400dFaulting package full name:Faulting package-relative application ID:Is that at all helpful? Still happens with beta 3.

I am running on W10 '166 x64, and when I install the beta, explore.exe crashes and relaunches repeatedly in rapid sucession. It did this on '159 as well. Anyone else?