New
#250
MBAM 3.0x with Anti-Exploit enabled breaks Edge pretty badly. It's a known issue (and some other 64bit browsers as well - reports have been for Chrome and something else).
MBAM 3.0x with Anti-Exploit enabled breaks Edge pretty badly. It's a known issue (and some other 64bit browsers as well - reports have been for Chrome and something else).
@Wynona
I see my Office Insider hasn't updated for weeks. Still at Version 1611 (Build 7416.1000) and I haven't known what may be the cause (haven't searched for a reason much, either.)
Which registry keys do you modify? And to what value? Thanks.
It seems that Insider Build 14986 is playing nicely with Vipre :)
Well, I did just reinstall everything last week, so the installer may have grabbed the latest build....
Hi,
Well, there's some good news and some not so good news.
Having created a bootable usb stick using the ISO file I decided it was time to put it to test.
It booted , launched setup but then it immediately complained about some "images" missing. A deja vu as I've seen this happen before.
Tried with a newly created stick but the exact same scenario. No cigar again so I decided to mount the ISO file from Windows, launch setup.exe from it and all went without a glitch. Go figure.
So, the ISO is usable to do an in place upgrade and quite probably as a source to repair a damaged image. Haven't tried the latter yet since there's nothing to repair... as yet. (sarc)
No clue what's wrong with my ISO, the ESD's Hash 1 is fine and I used ESD to ISO to create it. Even created a new one but no, it still won't play along. Strange.
Cheers,
Just my armchair tech knowledge here, but it seems like some bootable files could be missing when the ISO was created hence you can mount it and run setup.exe as that doesn't require booting of the flash drive, but when you have to boot it, you can't. So my guess is that some critical boot file or the bootable structure that makes it possible for the USB to boot is missing or messed up for some reason.
Best I could do with my non-programming knowledge.
Hope this helps.
Hi,
Thanks for the input.
It does boot and even goes as far as asking for a license key which you can skip but the it complains and it then reboots into Windows.
So, there's clearly something wrong with it. Wish I knew what though.
Later on today I'll extract the WIM file and try to look for some clues.
Cheers,
I do not know which encrypter / tool you have used to make the ISO, but if you are using the tool from our ESD to ISO tutorial, you are using an outdated, old version of it. A clear telltale is the ISO name:
The old tool named EN-US and EN-GB ISO images as:
- EN-US PRO x64: 14986.1000.160101.WINBUILD_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO
- EN-GB PRO x64: 14986.1000.160101.WINBUILD_CLIENTPRO_OEMRET_X64FRE_EN-GB.ISO
The current tool names ISO images as:
- EN-US PRO x64: en_windows_10_pro_14986_x64_dvd.iso
- EN-GB PRO x64: en-gb_windows_10_pro_14986_x64_dvd.iso
I have reminded and warned fellow members in tutorial thread several times, this extract from my post in mid June:
WarningThe tool has been updated 10 days ago, on June 5th. In case your tool is older please delete it from your PC simply by deleting the folder it was extracted to and download the updated tool. Download link in the first post (step 1.3).
Using the old outdated tool with 14XXX builds creates a not fully working ISO as some critical files are missing. My recommendation is to delete the ISO and old tool (just remove the folder), download the current version and finally redo ISO.
Kari