Windows 10: Can some one help with this Wierd PowerShell event log entry, Please

Looking through my power shell log i noticed a new entry:


HostApplication=powershell.exe -ExecutionPolicy Restricted -Command $Res = 0; ifGet-WindowsOptionalFeature -Online -FeatureName IIS-WebServerRole.State -eq 'Enabled' { $Path = $env:windir + '\system32\inetsrv\config\applicationHost.Config'; if Test-Path -Path $Path { try { [XML]$Xml = Get-Content $Path } catch { $Res = 1 } }; } Write-Host 'Final result:',$Res



Without user intervention we are observing the above activity in daily basis, kindly some one help me please, why it is happening daily.



Best Regards,

Kumar

:)

 

Moving an event log source is not having an effect

I'm having an issue that to be clear I'll describe in steps:

1. I created an event source called Foo in the event log called Application using the following powershell command:
   New-EventLog -source Foo -LogName "Application"
   
2. I could successfully log to the event log using that source.
   
3. Afterwards, I decided to remove the source and re-create it in a different event log:
   

The problem I'm having is that then when I run Write-EventLog -LogName "My App Log" -Source "Foo" -EventID 0 -EntryType Information -Message "Some message." the entry is logged to Application instead of to My App Log

Has anyone else experienced this behaviour? Am I missing anything?

 

powershell help does not seem to work

Thanks for response.
I have done chkdsk C: /f also.
still not working. I tried your suggestion also. That also does not work.
But as I said get-help dir works. Please see below

 

Export All Administrative Events to Excel

To analyze events, from the Windows Event Viewer, there is a simple way to export all Administrative Events to Excel, with PowerShell.

Exporting all Administrative Events to Excel is a simple two Step process, as described here:

Step 1 - Create the Administrative Events View .xml file

1. Open Eventviewer (%windir%\system32\eventvwr.msc)
2. Navigate to: Event Viewer (Local) > Custom Views > Administrative Events
3. In the “Actions” pane select “Filter Current Custom View”.
4. Select the the XML tab.
5. Press Ctrl+A to select all the XML code of the Custom View.
6. Open a notepad, paste the selected code and save the file to your Desktop as AdmEvtView.xml

Step 2 - Create the csv file with the events

1. Download the ExportEvtCSV.zip file, which contains the script ExportEvtCSV.ps1 and unzip it, on your Desktop.
   It's not a fancy script, just basic PowerShell commands to create a csv file on the Desktop.
2. In Windows Search, type “ISE” (without the quotes) to open “Windows PowerShell ISE” and Run as administrator
   
3. To allow running the script, change the ExecutionPolicy, for this session. To do that, in the Console pane type:
   Code:
4. In the Windows PowerShell ISE, open and run the script: ExportEvtCSV.ps1
   The script will create a csv file with a name YYYYMMDD.HHMM.csv on the Desktop
5. When done, open the newly created .csv file, format the columns as needed and optionally save it as .xlsx, if you wish.

That’s it! You now have all the Administrative Events in Excel for filtering and further analysis.

Now to the more technical hard stuff... *Confused

There is a reason for running the script from within PowerShell ISE!

It would be great if everything was also working perfectly, when running the script from an elevated PowerShell too.

We can run it from an elevated PowerShell, which means that you just follow the Step 1, as above but for the Step 2 instead of the ISE you run the script from an elevated PowerShell.

The problem is that it will work only for anybody who has en-US format for the dates. Everyone else, who has another format (i.e. en-GB, fr-FR, el-GR etc.), the dates are not translated properly by Excel (although the script uses the –UseCulture switch) and remain as text in the en-US format.

I'm not sure if this a bug of the "export-csv" cmdlet, but although it runs the way it supposed to from within the ISE, from PowerShell there is a problem with the dates format.
As I haven’t found a way to overcome this obstacle, any suggestion from the PowerShell gurus of the forum (like my good friend Shawn @Brink, for instance), is welcome.