saw that and did a little research here.. i figure that cortana has to be there. the only thing i can do is silence it and mark everything to lock/block/disable/etc. now, what about edge.. is that a way to completely remove it without messing the os?
I've just downloaded en_windows_10_business_editions_version_1809_updated_dec_2018_x64_dvd_f03937a3.iso (17763.194) and I'm puzzled over the 500Mb it grew over its previous "*_updated_sept_2018_x64_dvd_d57f2c0d" incarnation... and yep, I DID check the hashes on both ISOs. I didn't dive too much into analyzing this, beyond finding out that most of this growth went into boot.wim and install.wim. This is too much, IMHO, for a simple update of the same feature set. The ISO is 4.88Gb now ! Would someone pls enlighten me as to WTF MS$ has been doing here ...
It's the baseline 17763.1 iso with these updates pre-integrated by MSFT (not resetbased): Code: Package Identity : Package_for_KB4470502~31bf3856ad364e35~amd64~~10.0.1.2273 State : Installed Release Type : Update Install Time : 12/11/2018 3:19 AM Package Identity : Package_for_KB4470788~31bf3856ad364e35~amd64~~17763.164.1.1 State : Installed Release Type : Security Update Install Time : 12/11/2018 3:18 AM Package Identity : Package_for_KB4471331~31bf3856ad364e35~amd64~~10.0.1.0 State : Installed Release Type : Security Update Install Time : 12/11/2018 3:20 AM Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.194.1.5 State : Installed Release Type : Security Update Install Time : 12/11/2018 3:20 AM
On the october 17763.107 iso's the same. At least they now put in the same winre in all indices, they didn't on one of the previous official releases (iirc, the last non AiO they released). 17763.107 Consumer ISO en-US x64: Original: Code: Winre.wim: 439 MB (460,436,469 bytes) Boot.wim: 382 MB (400,988,824 bytes) Modified: Code: Winre.wim after rebuild: 369 MB (387,240,586 bytes) Winre.wim after rebuild and wimlib-imagex optimized: 364 MB (382,692,915 bytes) Boot.wim after rebuild: 328 MB (344,252,143 bytes) Boot.wim after rebuild and wimlib-imagex optimized: 323 MB (339,661,804 bytes)
Hello! Newbie here. Can someone please help me download the latest volume licence version of windows 10 pro 64 bit in en_us language that is activatable with a program like mtk? There are so many links and I am bit confused which one to download. I already downloaded the following ISO and what should be the next step before making bootable media? Is this an eval version which requires conversion to non-eval in order to activate? Moreover the iso name says updated_dec which means its already the latest build (17763.195) currently available or do I still have to mess with svf files? en_windows_10_business_editions_version_1809_updated_dec_2018_x64_dvd_f03937a3.iso Please help. Thanks.
That iso is exactly what you're looking for. You don't need anything else, just install the desired edition and activate it with any KMS solution. PS: the iso is 17763.194, which means that you're gonna have to run windows update. There are no oficial isos of 17763.195.
Update 1: Did a clean install again, and everyday installed a new driver and test it for that day, then installed another one (VGA>Audio>Chipset>etc...) Problem was RST Driver... . It happened even on newest RST drivers available on MSI Site (16.8.0.1000). so its using Windows default drivers. Update 2 (related to your problem): mine was doing the same thing. try to update ME Driver to 1842.12.0.1168 (available on MSI site) and clear your TPM chip through BIOS or Windows Security (Device Security>Security processor>Troubleshoot TPM Problems>Erase TPM.
Hi guys, I'm a sort of a noob. I bought a tablet with windows 10 home x64 and I want to install a modified image (by me) with MSMG tool. Can you point me to a clean windows 10 home x64 iso (english ) pls? I'm getting a bit confused looking at all the images in the first page and can hardly understand the difference between some of them. I'm looking for the right image so that when I install it, it'll be activated. I guess if I get the wrong version in won't be activated.
Just to clarify, are you saying that you can enable Core Isolation>Memory Integrity through the UI toggle in Defender, Windows 10 RS5/1809? Forcing it through the registry doesn't really count as you'll never know if it's actually properly working IMO. Because here it simply doesn't get enabled with the toggle, last BIOS, last IMEI drivers (there's some more recent that the ones you listed, you can find them on winraid forums, but even with the ones you listed it still doesn't work). As for TPM, I don't use it, I did try to see if that's the problem by enabling Intel PTT (onboard TPM 2.0 basically), but while the TPM worked fine and was recognized by Windows and Defender, Mem. Integrity still wouldn't be enabled. Thing is, I just couldn't find any use for TPM for my PC where I'm the only user and I really cannot find any reasons to encrypt the SSD, so I disabled it. Funny thing is, a HyperV RS5 VM will be able to enable MI through the toggle if configured correctly, which is saying to me that the firmware is doing something Defender doesn't like. Maybe. Or maybe it's the "Unallowed DMA capable bus/devices" in msinfo. Or maybe HSTI failing, can also see that in msinfo. The HyperV RS5 VM also fails HSTI though. Would be nice if somebody knew why it fails, but as much as I tried to find an answer, I got none. It also seems to pretty much fail (through the toggle) for anyone I've asked and bothered testing. PS: I'm using that Intel RST driver myself (standalone, not the whole software package). It works pretty flawlessly here, in fact, it got the 850 EVO SSD better scores in Magician.
Maybe it has something to do with the whole package of RST Driver. And yes, Core Isolation was enabled through the toggle, then it asked for a reboot and its working (tried to disabled it through the toggle and then enable again and it just works). Previous to the last Clean Install i've noted that in Event Viewer there were some errors from the TPM chip everytime I tried to enable Core Isolation; also and maybe not related but who knows i haven't installed Intel Chipset driver maybe it has something to do with it. Update: did a system image and Installed Intel Chipset Drivers and test it again Core Isolation activates and deactivates normally through the toggle. Haven't check RST Drivers... will be testing some hours maybe those minifreeze aren't back.
I'm confused, as the Intel Chipset "drivers" should theoretically just be .inf telling the OS how to name the Intel devices, no drivers at all. I got it installed too. I wonder what's going on. Mind sharing more details about the motherboard/CPU and the BIOS you have on them? Thanks. Also would be great if other people with 1809 would try the toggle and see if it works for them.
Can anyone tell me why is it that whenever I do an offline removal of Windows Defender (I tried it with Optimize-Offline and NTLite on an LTSC 2019 image), I always get the following error message towards the end of my installation: Windows could not complete the installation. To install Windows on this computer, restart the installation. I don't actually have to restart the installation, I just click OK and the installation finishes no problem. However, does this cause a hidden problem that I don't know about yet?