Conflicting lists. HOSTS file, missing or can't be edited, depending.

En el artículo , Paul
escribió:

HOSTS should not be empty.

s/h/it is using notepad and it's saved the file as hosts.txt.

--
(\_/)
(='.'=) systemd: the Linux version of Windows 10
(")_(")

En el artículo , Andy Burns
escribió:

There should only be 5 files in system32\drivers\etc (hosts,
lmhosts.sam, networks, protocol and services) the lmhosts.sam file is
just a template and not important unless you rename it to lmhosts

It's a hangover from M$'s theft of the BSD TCP/IP stack. Those files
are in /etc on UNIX systems. M$ needed somewhere to put them, so stuck
them in %windir%\system32\drivers\etc\ for reasons best known to
themselves.

--
(\_/)
(='.'=) systemd: the Linux version of Windows 10
(")_(")

On Mon, 06 Feb 2017 22:42:37 -0200, Shadow wrote:

On Mon, 06 Feb 2017 14:32:02 -0600, Char Jackson
wrote:

On Mon, 06 Feb 2017 17:23:16 -0200, Shadow wrote:

On Mon, 06 Feb 2017 09:42:45 -0600, Char Jackson
wrote:

He might be, but I note with interest that so far no one has answered
his question, have they? He asked "where do I use [localhost]", and so
far all I've seen are replies that talk about the hosts file. The hosts
file contains an entry for localhost, but localhost and the hosts file
are not at all the same thing.

It was replied to various times.
"localhost" means "on this computer"

It is usually put in the hosts file as

127.0.0.1 localhost #for IPV4
::1 localhost #for IPV6

but ANY IP can be used as localhost, but that would be a BAD
idea, for security reasons.

(if you don't use IPV6 for privacy reasons, comment out that
last line and use only IPV4)

If you want your network traffic to be contained inside your
computer, you use "localhost". A lot of programs use TCP for data
transfer and never go outside your computer. I can name a dozen.
[]'s

Refer to Message-ID:

micky said "I haven't been using localhost..."

you replied "You use "localhost" all the time...."

micky replied "don't be so cryptic. Where do I use it?"

***

Since then, there's been a lot of discussion about what localhost means,
what loopback means, and what the hosts file does, but still nothing
that answers the question.

The answer, for the vast majority of Windows users, will be that they
don't use localhost for anything at all. They may have programs or
processes that use it for interprocess communication, but most users
won't be aware of that or involved in any way.

A program I used this minute (Cherrytree) won't run if you
block localhost. It uses TCP to store my data. On my computer, of
course, it uses localhost to make sure it does not leak.
And almost all internet programs (Firefox included) use
localhost to work. So the CORRECT answer to the OP's question was "you
use it all the time".

I see what you're saying, but it's like I said above. You have programs
that use the loopback address to do what they need to do, but as a
computer user there are very, very few people who use localhost (or
loopback) for anything.

When you said "you use it all the time", I'm thinking you meant he has
applications that use it ('it' being localhost or more properly
loopback), and not that he (someone in userland) uses it. I read it as
meaning the second thing rather than the first. If you didn't mean it
that way, I apologize.

On Tue, 07 Feb 2017 00:33:00 -0600, Char Jackson
wrote:

On Mon, 06 Feb 2017 22:42:37 -0200, Shadow wrote:

On Mon, 06 Feb 2017 14:32:02 -0600, Char Jackson
wrote:

On Mon, 06 Feb 2017 17:23:16 -0200, Shadow wrote:

On Mon, 06 Feb 2017 09:42:45 -0600, Char Jackson
wrote:

He might be, but I note with interest that so far no one has answered
his question, have they? He asked "where do I use [localhost]", and so
far all I've seen are replies that talk about the hosts file. The hosts
file contains an entry for localhost, but localhost and the hosts file
are not at all the same thing.

It was replied to various times.
"localhost" means "on this computer"

It is usually put in the hosts file as

127.0.0.1 localhost #for IPV4
::1 localhost #for IPV6

but ANY IP can be used as localhost, but that would be a BAD
idea, for security reasons.

(if you don't use IPV6 for privacy reasons, comment out that
last line and use only IPV4)

If you want your network traffic to be contained inside your
computer, you use "localhost". A lot of programs use TCP for data
transfer and never go outside your computer. I can name a dozen.
[]'s

Refer to Message-ID:

micky said "I haven't been using localhost..."

you replied "You use "localhost" all the time...."

micky replied "don't be so cryptic. Where do I use it?"

***

Since then, there's been a lot of discussion about what localhost means,
what loopback means, and what the hosts file does, but still nothing
that answers the question.

The answer, for the vast majority of Windows users, will be that they
don't use localhost for anything at all. They may have programs or
processes that use it for interprocess communication, but most users
won't be aware of that or involved in any way.

A program I used this minute (Cherrytree) won't run if you
block localhost. It uses TCP to store my data. On my computer, of
course, it uses localhost to make sure it does not leak.
And almost all internet programs (Firefox included) use
localhost to work. So the CORRECT answer to the OP's question was "you
use it all the time".

I see what you're saying, but it's like I said above. You have programs
that use the loopback address to do what they need to do, but as a
computer user there are very, very few people who use localhost (or
loopback) for anything.

When you said "you use it all the time", I'm thinking you meant he has
applications that use it ('it' being localhost or more properly
loopback), and not that he (someone in userland) uses it. I read it as
meaning the second thing rather than the first. If you didn't mean it
that way, I apologize.

I meant it as the first, he is unaware he is using loopback,
but his apps use it all the time.
[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012

In alt.comp.os.windows-10, on Mon, 06 Feb 2017 17:12:45 -0200, Shadow
wrote:

On Sun, 05 Feb 2017 18:53:09 -0500, micky
wrote:

First, how important in Win10 are the files and etc subdirectory in
C:\windows\system32\drivers??

I regularly wipe this directory. eGnerally it contains old stuff.

Good to know.

Unless Win 10 uses some new scheme, that will brick your PC. I
think the OP meant it as a joke.

Thanks.

That was an obnoxious thing to do Norman. What if Shadow hadn't
posted?

[]'s

In message , Mike Tomlinson
writes:
En el artículo , Paul
escribió:

HOSTS should not be empty.

s/h/it is using notepad and it's saved the file as hosts.txt.

If you save a file in notepad without an extension, it will save it as a
..txt file. In order to save it without, you might have to use quotes -

"hosts"

- or possibly even

"hosts."

(note the dot). If neither of those work, you'll just have to let it
save as hosts.txt, then delete the old hosts file and rename the new one
by trimming the .txt part.

A lot of prog.s add their default extension - sometimes even if you add
another one; for example, I think if you try to save from notepad x.bat,
you'll get x.bat.txt - unless you put it in quotes. (In some cases,
changing the "save as" - the dropdown list usually next to the filename
box - to "all files" or similar helps.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

the plural of 'anecdote' is not 'evidence'. Professor Edzart Ernst, prudential
magazine, AUTUMN 2006, p. 13.

In alt.comp.os.windows-10, on Mon, 06 Feb 2017 12:01:39 -0000, "Kerr
Mudd-John" wrote:

On Sun, 05 Feb 2017 23:51:53 -0000, micky wrote:

In microsoft.public.windowsxp.general, on Sun, 05 Feb 2017 21:00:00
-0200, Shadow wrote:

On Sun, 05 Feb 2017 16:35:48 -0500, micky
wrote:

In microsoft.public.windowsxp.general, on Sun, 5 Feb 2017 18:28:06
+0000, Andy Burns wrote:

micky wrote:

Shadow wrote:

You use "localhost" all the time....

If you had said, You use 127.0.n.n all the time, we woudln't have had
such an interesting thread.

Well, if so, it's working. But don't be so cryptic. Where do I use
it?

Every time you visit a website, or make any TCP/IP connection, windows
will look in hosts to see if there's an entry there for the host
you're
connecting to, before doing a DNS query if it's not.

Unless it's a numerical IP, like the ones Win 10 uses for
"telemetry".

Okay. And like the numerical IPs I use in Forte Agent and Eudora.

I think not if you specify the IP address, 127.0.0.1 for example. Why
look up a name if the number has already been given?

You can use

192.168.0.1 localhost

point everything local there and make your network adapter
192.168.0.2, but why complicate something that's worked fine (and is
the default) for decades ?

I didn't use 192.168... but I did use 127.0.0.2 because I need to
distinguish mail server messages from Forte Agent from those from
Eudora, which uses 127.0.0.1.

I was going to use localhost2 in Agent, and put a line in the hosts file
to resolve that to 127.0.0.2, but I got delayed modifying the hosts
file. The previous paragraph and this one are what I meant by more
than one way to do this.

[]'s

Yet earlier you asked:

There is no contradiction here. I WAS going to use locahost2, but I
got delayed inserting in the hosts file and now, even though it's in the
hosts file, it's not used. It's not specified anywhere and no call to
the hosts file will use that line. And localhost is not specified
anwhere either.

Quote
In microsoft.public.windowsxp.general, on Sun, 05 Feb 2017 07:00:48
-0200, Shadow wrote:

On Sun, 05 Feb 2017 00:35:23 -0500, micky
wrote:

I haven't been using localhost or 127,0 so I don't know how well its
handled, but see my next comment.
You use "localhost" all the time....

Well, if so, it's working. But don't be so cryptic. Where do I use it?

I comment out the line for IPV6.
[]'s
UnQuote


Methinks he's trolling.

Does "he" refer to me or Shadow? If you mean me, you shouldn't be so
quick to suggest someone is trolling, because you haven't understood the
thread.

In alt.comp.os.windows-10, on Mon, 06 Feb 2017 17:05:41 -0200, Shadow
wrote:

On Sun, 05 Feb 2017 18:46:27 -0500, micky
wrote:

I've restored these 4 lines of yours that you snipped because they are
relevant:
so they don't leak data intended for your computer
only. (unless they are fed a numerical IP, which Win 10 and any other
decent trojan/malware does to bypass your hosts file and phone home
with your personal data, but that is besides the point).

I note that you call win10 malware,
I posted to both XP and 10 because I thought the topic of conflicting
lists of filess from different file managers related to people in both
groups, but I am using 10, so it seems like you're saying that 10
bypasses the hosts file. If that is exemplifed by those 3 lines then
so does 7 and probably 8 and 8.1, because the link Paul first gave shows
that they too are malware because 7, at least, also includes

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

None of them "bypass" the hosts file. They don't need it if

You said it. I'm just using your terminology. In the 4 lines that I
restored: "which Win 10 and any other decent trojan/malware does to
bypass your hosts file "

the remote site name has already been resolved no a numerical IP.

Study what DNS means.

The meaing of DNS is not at issue. Don't attempt to be patroniziong.
This is the second time in this thread you've tried that, and if it were
not the second time, I would not point out that we've tried 7 times to
explain that I don't use localhost and I'm still not sure you got it or
not after the 8th time.

As to malware, the most widely accepted definition is:

"Malware, short for malicious software, is any software used to
disrupt computer or mobile operations, gather sensitive information,
gain access to private computer systems, or display unwanted
advertising."

And you think this describes Windows 10?

Sound familiar ?


[]'s

In alt.comp.os.windows-10, on Sun, 05 Feb 2017 21:00:00 -0200, Shadow
wrote:

On Sun, 05 Feb 2017 16:35:48 -0500, micky
wrote:

In microsoft.public.windowsxp.general, on Sun, 5 Feb 2017 18:28:06
+0000, Andy Burns wrote:

micky wrote:

Shadow wrote:

You use "localhost" all the time....

Well, if so, it's working. But don't be so cryptic. Where do I use it?

Every time you visit a website, or make any TCP/IP connection, windows
will look in hosts to see if there's an entry there for the host you're
connecting to, before doing a DNS query if it's not.

Unless it's a numerical IP, like the ones Win 10 uses for
"telemetry".

I think not if you specify the IP address, 127.0.0.1 for example. Why
look up a name if the number has already been given?

You can use

192.168.0.1 localhost

You're so wrapped up in the hosts file here that you give an example
of this line which would be in it, and you ignore what I said, Why look
up a name, like localhost, if the number has already been given,
192.168.0.1 or 127.0.0.1 or any such number. The point is, one more
time, that if someone gives the IP number there will be no need to look
in the hosts file which translates names to numbers, when no name was
given to translate, and the number was already given.

point everything local there and make your network adapter
192.168.0.2, but why complicate something that's worked fine (and is
the default) for decades ?
[]'s

In alt.comp.os.windows-10, on Mon, 06 Feb 2017 14:32:02 -0600, Char
Jackson wrote:

On Mon, 06 Feb 2017 17:23:16 -0200, Shadow wrote:

On Mon, 06 Feb 2017 09:42:45 -0600, Char Jackson
wrote:

He might be, but I note with interest that so far no one has answered
his question, have they? He asked "where do I use [localhost]", and so
far all I've seen are replies that talk about the hosts file. The hosts
file contains an entry for localhost, but localhost and the hosts file
are not at all the same thing.

Exactly. It's nice that hou understand what was said.


It was replied to various times.
"localhost" means "on this computer"

That is irrelevant. Localhost, both with and without quotes, may mean
"on this computer", but "On this computer" does not mean "localhost".

"Localhost" is a nickname, an alternative name, for "on this computer"
but just as George Bush might have the nickname Skippy, if I call him
George or Mr. Bush, and I don't call him Skippy, I'm not using Skippy.

That Skippy means George Bush does not mean that I am using the name
Skippy when I use George.

Since I'm not using Skippy, it doesn't matter to me what Skippy means,
just as, Since I'm not using localhost, it doesn't matter to me what
localhost means, whether it's defined in the hosts file or, as the
comment in hosts files (later than xp?) says, "localhost name resolution
is handled within DNS itself." There is no localhost name resolution
if there is no localhost name. If there is a number instead, there is
nothing to resolve.

It is usually put in the hosts file as

127.0.0.1 localhost #for IPV4
::1 localhost #for IPV6

but ANY IP can be used as localhost, but that would be a BAD
idea, for security reasons.

(if you don't use IPV6 for privacy reasons, comment out that
last line and use only IPV4)

If you want your network traffic to be contained inside your
computer, you use "localhost". A lot of programs use TCP for data
transfer and never go outside your computer. I can name a dozen.

None of these 10 lines have anything to do with it.

[]'s

Refer to Message-ID:

micky said "I haven't been using localhost..."

you replied "You use "localhost" all the time...."

micky replied "don't be so cryptic. Where do I use it?"

***

Since then, there's been a lot of discussion about what localhost means,
what loopback means, and what the hosts file does, but still nothing
that answers the question.

The answer, for the vast majority of Windows users, will be that they
don't use localhost for anything at all. They may have programs or
processes that use it for interprocess communication, but most users
won't be aware of that or involved in any way.

Personally, I used localhost to test a web server in the late 90's and
an FTP server around 2003, but I haven't used it since then. I'm
thinking most people would correctly say that they've never used it at
all, which is pretty far from "you use localhost all the time".

In alt.comp.os.windows-10, on Tue, 07 Feb 2017 09:50:07 -0200, Shadow
wrote:

On Tue, 07 Feb 2017 00:33:00 -0600, Char Jackson
wrote:

On Mon, 06 Feb 2017 22:42:37 -0200, Shadow wrote:

On Mon, 06 Feb 2017 14:32:02 -0600, Char Jackson
wrote:

On Mon, 06 Feb 2017 17:23:16 -0200, Shadow wrote:

On Mon, 06 Feb 2017 09:42:45 -0600, Char Jackson
wrote:

He might be, but I note with interest that so far no one has answered
his question, have they? He asked "where do I use [localhost]", and so
far all I've seen are replies that talk about the hosts file. The hosts
file contains an entry for localhost, but localhost and the hosts file
are not at all the same thing.

It was replied to various times.
"localhost" means "on this computer"

It is usually put in the hosts file as

127.0.0.1 localhost #for IPV4
::1 localhost #for IPV6

but ANY IP can be used as localhost, but that would be a BAD
idea, for security reasons.

(if you don't use IPV6 for privacy reasons, comment out that
last line and use only IPV4)

If you want your network traffic to be contained inside your
computer, you use "localhost". A lot of programs use TCP for data
transfer and never go outside your computer. I can name a dozen.
[]'s

Refer to Message-ID:

micky said "I haven't been using localhost..."

you replied "You use "localhost" all the time...."

micky replied "don't be so cryptic. Where do I use it?"

***

Since then, there's been a lot of discussion about what localhost means,
what loopback means, and what the hosts file does, but still nothing
that answers the question.

The answer, for the vast majority of Windows users, will be that they
don't use localhost for anything at all. They may have programs or
processes that use it for interprocess communication, but most users
won't be aware of that or involved in any way.

A program I used this minute (Cherrytree) won't run if you
block localhost. It uses TCP to store my data. On my computer, of
course, it uses localhost to make sure it does not leak.
And almost all internet programs (Firefox included) use
localhost to work. So the CORRECT answer to the OP's question was "you
use it all the time".

If this post seems like overdoing it, I'm sorry, but it was already
written before I decided the other ones might be enough.

I see what you're saying, but it's like I said above. You have programs
that use the loopback address to do what they need to do, but as a
computer user there are very, very few people who use localhost (or
loopback) for anything.

When you said "you use it all the time", I'm thinking you meant he has
applications that use it ('it' being localhost or more properly
loopback), and not that he (someone in userland) uses it. I read it as
meaning the second thing rather than the first. If you didn't mean it
that way, I apologize.

I meant it as the first,

However I used the term localhost first and now you say you then used it
with a different meaning when you tried to contradict me. You should
have used the same meaning but since you didn't realize that you had
used a different meaning, the rest of this thread, 3 attempts by me and
3 by Char, have been to get you to at least see that by using it with a
different meaning than I used, you did not contradict me. I haven't
been using localhost. As I said, I used the term 127.0.0.1 but not the
term localhost.

he is unaware he is using loopback,

Again you're changing the terminology to make an irrelevant point as if
it were relevant. I never said I didn't use loopback, or that I didn't
use 127.0.0.1 or a similar number, or that I didn't use something that
meant "on this computer". I said I didn't use localhost and I
don't.

If instead you mean that I'm unaware of the exact microsecond when I'm
using loopback, that I'll grant you, but of course I know I'm using
loopback. .
but his apps use it all the time.

This has nothing to do with localhost, or localhost2, which I also
mentioned.

[]'s

In alt.comp.os.windows-10, on Sun, 05 Feb 2017 20:54:20 -0200, Shadow
wrote:

On Sun, 05 Feb 2017 16:32:55 -0500, micky
wrote:

In microsoft.public.windowsxp.general, on Sun, 05 Feb 2017 14:25:03
-0500, Paul wrote:

micky wrote:
In microsoft.public.windowsxp.general, on Sun, 05 Feb 2017 07:00:48
-0200, Shadow wrote:

On Sun, 05 Feb 2017 00:35:23 -0500, micky
wrote:

I haven't been using localhost or 127,0 so I don't know how well its

This was a mistake. Of course I'm using 127, but I haven't been using
locahost. I don't know if that gets Shadow off the hook or not.

It's not 127, it's 127.0.0.1 (or 0.0.0.0 in Win 7 or worse
versions of windows)
And yes, all net-aware programs check your hosts file before
doing a DNS lookup so they don't leak data intended for your computer
only. (unless they are fed a numerical IP, which Win 10 and any other
decent trojan/malware does to bypass your hosts file and phone home
with your personal data, but that is besides the point).
You need 127.0.0.1 (or 0.0.0.0) in your hosts file, or windows
will not function correctly.
You DON'T need
::1 localhost
I comment it out and disable IPV6.
[]'s

handled, but see my next comment.
You use "localhost" all the time....

Because here he doesn't refer to 127 but specifically to localhost.

Well, if so, it's working. But don't be so cryptic. Where do I use it?

OK, article.

https://en.wikipedia.org/wiki/Localhost

"Name resolution

IPv4 network standards reserve the entire 127.0.0.0/8
address block for loopback purposes. That means any packet
sent to one of those 16,777,214 addresses (127.0.0.1 through
127.255.255.254) is looped back. IPv6 has just a single address, ::1.
"

I grant that I use 127.0.0.1, but how does that mean I use localhost.
In places I've seen I used the number. Localhost is just an easier to
remember name that has to be translated to the number anyhow.

I don't know what could be more clear than this last sentence by me, but
you didn't respond to it. Maybe you didn't see it, I have not avoided
telling you how I use the word.

Now, imagine you just installed your own IIS web server

[the rest of Paul's post snipped]

On Tue, 07 Feb 2017 19:21:28 -0500, micky
wrote:

In alt.comp.os.windows-10, on Mon, 06 Feb 2017 17:05:41 -0200, Shadow
wrote:

On Sun, 05 Feb 2017 18:46:27 -0500, micky
wrote:

I've restored these 4 lines of yours that you snipped because they are
relevant:
so they don't leak data intended for your computer
only. (unless they are fed a numerical IP, which Win 10 and any other
decent trojan/malware does to bypass your hosts file and phone home
with your personal data, but that is besides the point).

I note that you call win10 malware,
I posted to both XP and 10 because I thought the topic of conflicting
lists of filess from different file managers related to people in both
groups, but I am using 10, so it seems like you're saying that 10
bypasses the hosts file. If that is exemplifed by those 3 lines then
so does 7 and probably 8 and 8.1, because the link Paul first gave shows
that they too are malware because 7, at least, also includes

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

None of them "bypass" the hosts file. They don't need it if

You said it. I'm just using your terminology. In the 4 lines that I
restored: "which Win 10 and any other decent trojan/malware does to
bypass your hosts file "

I meant "don't use". IOW, you cannot block Win 10 from phoning
home using a hosts file, since it does not use it. Ditto with most
modern trojans.
You need a firewall for that.

the remote site name has already been resolved no a numerical IP.

Study what DNS means.

The meaing of DNS is not at issue.

Ah, but it IS. It's what your hosts file does. It's how your
programs know localhost is at 127.0.0.1.

Don't attempt to be patroniziong.
This is the second time in this thread you've tried that, and if it were
not the second time, I would not point out that we've tried 7 times to
explain that I don't use localhost and I'm still not sure you got it or
not after the 8th time.

As to malware, the most widely accepted definition is:

"Malware, short for malicious software, is any software used to
disrupt computer or mobile operations, gather sensitive information,
gain access to private computer systems, or display unwanted
advertising."

And you think this describes Windows 10?

Disrupt computer or mobile operations = updates paralizing the
OS, sometimes at critical moments
gather sensitive information = telemetry
gain access to private computer system = yes
display unwanted advertising = bingo, all 4 !!!
[]'s

Sound familiar ?


[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012

On Tue, 07 Feb 2017 19:28:21 -0500, micky
wrote:

In alt.comp.os.windows-10, on Sun, 05 Feb 2017 21:00:00 -0200, Shadow
wrote:

On Sun, 05 Feb 2017 16:35:48 -0500, micky
wrote:

In microsoft.public.windowsxp.general, on Sun, 5 Feb 2017 18:28:06
+0000, Andy Burns wrote:

micky wrote:

Shadow wrote:

You use "localhost" all the time....

Well, if so, it's working. But don't be so cryptic. Where do I use it?

Every time you visit a website, or make any TCP/IP connection, windows
will look in hosts to see if there's an entry there for the host you're
connecting to, before doing a DNS query if it's not.

Unless it's a numerical IP, like the ones Win 10 uses for
"telemetry".

I think not if you specify the IP address, 127.0.0.1 for example. Why
look up a name if the number has already been given?

You can use

192.168.0.1 localhost

You're so wrapped up in the hosts file here that you give an example
of this line which would be in it, and you ignore what I said, Why look
up a name, like localhost, if the number has already been given,
192.168.0.1 or 127.0.0.1 or any such number. The point is, one more
time, that if someone gives the IP number there will be no need to look
in the hosts file which translates names to numbers, when no name was
given to translate, and the number was already given.

Sorry, couldn't follow you there...
[]'s

point everything local there and make your network adapter
192.168.0.2, but why complicate something that's worked fine (and is
the default) for decades ?
[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012

En el artículo , J. P. Gilliver
(John) escribió:

If you save a file in notepad without an extension, it will save it as a
.txt file. In order to save it without, you might have to use quotes -

Yes, thank you for clarifying my post. I was suggesting, somewhat
obliquely, that the OP may not have realised that his/her saving a file
s/he thinks is called "hosts" may actually have been saved as
"hosts.txt" because of Notepad's daft default behaviour.

Windows hiding file extensions only serves to add to the confusion. I
have this turned off. Tools, Folder Options, View, untick "hide
extensions for known file types".

It's worth noting that some anti-virus makes the hosts file read-only,
which doesn't help. I have a feeling Win10 also does this by default,
but don't use it so am not sure.

--
(\_/)
(='.'=) systemd: the Linux version of Windows 10
(")_(")