Windows 10: PowerShell fails to launch excel with CLSID COM error

Hi Community,Really simple issue here we cannot figure out:1. Since 2015, Microsoft released this functionality and is officially documented here2. When we try to run the command in PowerShell below this is what happens:$excel = New-Object -ComObject Excel.ApplicationNew-Object : Retrieving the COM class factory for component with CLSID {00000000-0000-0000-0000-000000000000} failed due to the following error: 80040154 Class not registered Exception from HRESULT: 0x80040154 REGDB_E_CLASSNOTREG. + CategoryInfo : ResourceUnavailable: : [New-Object], COMException + FullyQualif

:)

 

Powershell Clsid.

Hello! I Found The Clsid For The Command Prompt, Which Is

CommandFolder.{437ff9c0-a07f-4fa0-af80-84b6c6440a16} I Was Wondering If There Was A Powershell Clsid, And If So What Is It? Thank You!

 

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.

 

PowerShell does not launch bash.exe

All,

I
am new and trying to learn.

My
issue: When I enter bash.exe in a PowerShell cmd window, my PC does not launch the Ubuntu command. I think Windows Subsystem for Linux (WSL) is not in my $ENVath.

Troubleshooting
I have done:

1. Reading
   on the Internet, I can test my $ENVath by typing the following a PowerShell cmd:
   

PS C:\WINDOWS\system32>
where.exe calc

C:\Windows\System32\calc.exe

It returned the follow:

PS C:\WINDOWS\system32>
calc

(And the calculator displayed
on my PC)

1. Reading
   on the Internet, I can also test my $ENVath by typing the following a PowerShell cmd:
   

PS C:\WINDOWS\system32>
where.exe wsl

It returned the follow:

INFO: Could not find
files for the given pattern(s).

Here
is the output of $ENVath

PS
C:\WINDOWS\system32> $ENVath

C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program
Files (x86)\Calibre2\;C:\Program Files\PuTTY\;C:\Program Files\Microsoft VS Code\bin;C:\Users\user-lenovo595\AppData\Local\Microsoft\WindowsApps

Question:

What
would you suggest as my next step to fix the issue?

Thank
you,