Preventing select-string from adding additional undesired strings in the output file

Question

Hi friends
in PS 4.0 i am trying to write a function which
step1: export the list of all eventlogs ----> wevtutil el > "$home\documents\\loglist1.txt"
step2: deleted the following two lines from loglist1.txt
DebugChannel
Microsoft-RMS-MSIPC
( the reeson of deleting these two lines is wevtutil cl command, can't clear these two evenlogs among approximately 1000 logs)
in fact via select-string with -pattern -notmatch parameters, we select anything except these two line
step3:  pastes the select-string contents into the same file ("$home\documents\loglist1.txt") or into new text file (for example
"$home\documents\loglist2.txt")
here is my code:
function MycleareventsAll {
cls
Wevtutil el > "$home\documents\loglist1.txt"
$mycontents = select-string "$home\documents\loglist1.txt" -pattern DebugChannel, Microsoft-RMS-MSIPC -NotMatch
cd "$home\documents\"
$mycontents | out-file loglist2.txt"
# also i tried ---> $mycontents | set-content "loglist2.txt"# also i tried ---> $mycontents | set-content "loglist1.txt"
but the problem is, in addition of deletion, unfortunatelly additional strings (filepath, filename, line number) are added into the final text file so wevtutil will fail clearing logs listed in text file.
here is contents of the final text file
C:\Users\Administrator\documents\loglist.txt:1:Analytic
C:\Users\Administrator\documents\loglist.txt:2:Application
C:\Users\Administrator\documents\loglist.txt:4:DirectShowFilterGraph
but i need the contents be the same as original file without that two specific line:
Analytic
Application
DirectShowFilterGraph
i searched but i didn't find a way to prevent select-string cmdlet from adding these edditional strings
(filepath, filename, line number) into output file while keeping the original contents.
note: -quiet parameter is not what i want. it removes all contents & simply inserts a true or false.
any help? 

Answer 1

don't forget that Guys here know the basics of security such as clearing event logs & ...
how odd if you don't know this.
clearing all events is useful in test environment for example when i ma teaching my students & need to see all newly created events & work on them
Then you are teching your students how not to use an event log.  We use filters and queries to access event logs.  We also use event log CmdLets in PowerShell.  WEVTUTIL is ok but it does not marry wellwith PowerShell as you have seen.
I have found very few people who are not certified in WIndows administration that know much about eventlogs when it should be a ver important part of administration.  PowerShell has mmade EL management much easier but few take the time to learn how
to use the EL support in PowerShell.
I see no point inclearing event logs.  It accomplishes nothing.
¯\_(ツ)_/¯
oh your are introducing me filters & queries in event viewer !! please stop Laughing me this way.
your problem is you judge about people's knowledge & you persist on your absurd judgments.
look at your sentence:
"Then you are teaching your students how not to use an event log" 
where from you tell this? have you been present in my classes to see what i teach to my students?
have you seen that i told to my students not to use event viewer?
my goal of clearing events is related to myself. it's non of your businesses.
people are not interested to here concurrent irrelevant advises from you like a grandmother. they are searching for a solution. their intent of doing tasks is not up to you.