Thanks. Keep in mind, an UPGRADE -- that means to say, when Windows 10 handles the licensing didn't work -- so either it did not like the SLIC 2.4, or it did not like that I left the hardware with exclamation points. But I'm not going to try it again because I don't want to install the hardware in Win7 -- only then to have to fiddle with uninstalling it in Win10 and re-installing Win10 drivers. I bought a grey market key this time around. Oh well.
The genuineticket.xml shortcut is actually the same as a full upgrade, at least the same steps are done to create the ticket but at real upgrade it's handled by the upgrade. Why not put in a spare hdd and do the upgrade or genuineticket.xml method on that hdd, after establishing the hwid you're original install should be able to pick-up the HWID. so, actually you post a lot of rubbish only to post next you sponsored a fraud by buying a (probably illegally obtained) key from him.
Enth know about correct things here in MDL a lot of time this already talk about a lot of times;maybe someone need READ more
No, it can be good, but the created iso will always have it's own unique SHA-1, so it never can be verified.
Yes, I have the utmost respect for him, but time was not on my side. If I ever replicate the build, I'll have to experiment again. For what it's worth, I tried an SLIC 2.1 BIOS instead of 2.4, that didn't change anything. The only other thing I could have done was perhaps to install an INF update... Maybe next time. I wasn't having luck with DISM /add-driver either. It adds successfully, but booting Windows reflects no change. Luckily AsRock had PS/2 emulation in the BIOS, because I didn't bring a spare mouse with me. The upgrade was from an Asus H61 to an AsRock Z370 board. Another thing: I had a tremendous endeavour in getting Win7 to boot after the board swap. This probably had something to do with Ghost getting confused with the UEFI mode. When Ghost was launched in a UEFI PE, it asked me if I wanted it to convert the target disk to UEFI, because it detected the UEFI file system. I pressed no, and after the clone, windows booted with 0x0000007B, no matter how much I fiddled with the registry. I'm almost certain doing the ghost from a non-UEFI PE solved it.
What do the slic versions have to do with generating a HWID for 10? If win 7 SP1 install is activated and at least the generic drivers are installed, just upgrade to 10 or go the gatherosstate.exe route.
I didn't think they had anything to do with it, but I was not 100% certain. The reason is that in the early days of SLIC activation, it was thought that using an SLIC >2.1 to activate 2.1 could potentially be detected in the future and blocked. Yes, I agree I could have installed the drivers, but I didn't have time to experiment, and I didn't want Win7 drivers contaminating the Windows 10 install (I had to use the upgrade method here)... For example, Intel USB3 drivers are blocked on Windows 10, I didn't want problems.
If I try to upgrade a 16299.431 Windows 10 Enterprise x64 to a 17134.81 one by running the setup.exe file I only have the keep personal files only option (I have to choose the keep personal files and apps option). I can't choose this option in this PC (the computer isn't mine) and I can't do a clean install also so what should I do? This is strange since in my PC I did this and I could choose the keep personal files and apps option. EDIT: The RS4 update didn't come (I don't know why it takes so long) so if I downgrade the Enterprise edition to Pro (for example) by inserting a key and then run the setup.exe from the 17134.81 Enterprise edition to upgrade it to RS4 (and afterwards if I have the Pro edition I insert an Enterprise key to have the Enterprise edition) will I be able to choose the keep personal files and apps options? EDIT 2: Never mind, it didn't work. Maybe it has to do with the default system UI language and the installed language. Strange, I have two (pt-BR and en-GB) installed languages according to DISM /online /get-intl when I should only have one (pt-BR) and the en-GB is the default one and not the pt-BR. Also, when I go to language options I only have the pt-BR language and not it and the en-GB language. The ISO is a pt-BR one. How can I remove an installed language when it only shows up in DISM /online /get-intl? Lpksetup.exe /u en-GB says uninstall failed! EDIT 3: I couldn't remove the en-GB language but I managed to set the pt-BR one as default and afterwards I could use the keep personal files and apps option and upgrade Windows 10 to RS4. EDIT 4: I successfully removed the en-GB language. I don't know why Lpksetup.exe was able to remove it this time.
What is the official SHA-256 for these two? en_windows_10_business_editions_version_1803_updated_march_2018_x64_dvd_12063333.iso en_windows_10_consumer_editions_version_1803_updated_march_2018_x64_dvd_12063379.iso
Another question, and what if I upgrade RS4 to RS5 or do a clean RS5 install? Will the exceptions be kept? And if they do some changes in Windows Defender or if I uninstall it and reinstall it (I don't know if it's possible)? Would I have to manunally add them in the future?
By upgrade the settings probably stay, by clean install it never can, it's a clean install, in case of clean install you have to set the exclusion again.
So, even if I did a clean RS4 install I'd have to manually add the files to Windows Defender exclusions' or I'd have to do that if I did a clean RS5 install (in case it's the last situation I'd have to wait for the activator's developer to support RS5, right?)? They are only added if I do an ugrade install? EDIT: Now I have another question, I want to install an edited RS3 (by MSMG ToolKit) Windows 10 version which has the same edition as the current install and without losing files and apps (only the "garbage" wich comes with the unedited versions). What will be the results? Will I have the apps wich come up with Windows 10 or nor? And what about the configuration? Will it be the prior or the new one?
To be short, when a clean install is performed not any thing, settings or files, will be there after install. You have to set the exclusions again, in all cases just verify if they are there and set them again if they were gone.