CliffS

have you checked all cable seating(specially the ones connected to the PSU, and if at all possible try another PSU(borrow a friends)), also if you have a discrete GPU, try disconnecting it, and using the CPU's Integrated graphics, to see if the GPU is causing problems at boot, as PCIe talks directly to the CPU.

Do you have a CMOS Reset button or pins that you can short out on your motherboard? You have a K SKU I see, and if you have a bad overclock, or the CMOS, or your BIOS/UEFI profile got corrupted, a reset to all defaults of your currently installed BIOS version might help. This happened to me after I tried pushing my 6700K to the limit, using one single core, hyperthreading turned off, to reduce heat(I use fans, not water), and could validate 5.18986 GHz in CPU-Z. The system booted into Windows still, but for the life of me, I could not get back into BIOS to revert back to my normal/daily 4.9GHz with all cores and HT on. A CMOS reset helped, I thought I was bricked though, until I remembered to try this

Thanks Dashke, these are real nice, I have added them to my Malwarebytes wallpapers-theme folder

Thanks

Hi 41149512O welcome to Malwarebytes. go to the settings tab and unselect system tray tooltips:

Yeah I meant 1297 and caught it after I posted. Luckily, I made the time limit to edit the post You posted while I was making the changes, but thanks for informing in case I hadn't caught it.

Experimental Build 1.09.1.1297 installed and working great on Windows 10 Insider build 14986.1001 and Current Branch 14393.576. I had no problems with any browser loading immediately after install( I always just upgrade over the old MBAE build by the way).

Happy New Year from Bamberg Germany

MBAE alpha build 1.09.1.1294 is working very well for me on all four of my Windows 10 systems, one of which is insider build 14986.1001, the other three current build 14393.576. Just a small tip for those using Edge: If Edge freezes, or crashes, right after installing a new beta, on top of the old, try rebooting Windows and retry opening it. I'm beginning to think, that, because even if Edge is closed, it is deeply hooked into Windows and some components/APIs might be in use, so the WinSxS folder cannot be updated until a restart(PendingFileRenameOperations). This happens once in a while to me, but not often, that's why I think it might be a background quirk. This is just an educated guess, from install other software in the past, but I am far from an expert, just a lowly Windows geek

Merry Christmas to all the Malwarebyters Darth Santa might be a little late today, he had to squash a Elf rebellion at the Hoth Pole last night. Here is a photo I took:

Thank you, I'm happy you like it

Ok time for a new one with the release of Malwarebytes 3.0

You're both welcome

Hi, I just noticed that the version number shown here: https://www.malwarebytes.com/adwcleaner/ is wrong as it shows Version 6.030, but when you click the download button and get sent to ToolsLib for the download, it says 6.040. I just thought I might mention it

Experimental Build 1.09.1.1266 running well on Windows 10 Insider Build 14971.1000, no Edge crashing. Now that Microsoft has added an epub reader to Edge, I wanted to see if MBAE would say "Hey what's this!", so I went and looked at an epub version of Deployment guide for SharePoint Server 2010 here: http://download.microsoft.com/download/3/B/F/3BF70FE5-83FD-4A26-AC19-EBF94EE312E5/Deployment-guide-for-Microsoft-SharePoint-Server-2010.epub and MBAE excepted the new "toy" no problem/no blocks.