-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hosts file should not be used on Windows 10, will break Internet #87
Comments
Really sorry you had to go through that. I've added a warning next to the download link. Would booting into a different OS allow you to edit and repair the file without needing to enter safe mode? |
Possibly, I don't know. The SecureBoot security feature makes it non-trivial to boot into a different OS. I failed to boot a Ubuntu from USB. To achieve this I had to disable Bitlocker (Windows' built in full-disk-encryption that is enabled by default these days, and which also integrates SecureBoot). To disable Bitlocker (which btw I also had to do when I tried rebooting in Windows safe mode to remove the hosts file), you can't just go in UEFI and change asetting. After you do this, you will be asked to enter the decryption key, which is saved on Microsoft's website. So gotta go on a different computer, go to https://aka.ms/recoverykeyfaq, log in with MS account (not sure how people without a Microsoft account can do it), write down a huge decryption key, enter it on the target Windows computer. |
Is opening as empty for me for some reason; is there a reason why? |
Windows nearly chokes on hosts files of 1MB, and it seems this issue is exponential, because blockconvert's 50MB hosts file appears to break Windows perpetually.
If you put the 50MB hosts file in c:/windows/system32/drivers/etc/hosts, the DNS Client service will begin using 25% CPU perpetually. No DNS lookups will work. You can't even open the start menu to search for a program because apparently that relies on network lookups too.
A working fix if you opened this can of worms:
What a joke of an OS.
The text was updated successfully, but these errors were encountered: