Windows 10: I used administrator PowerShell to uninstall OneDrive, and all my files saved in the...

I used administrator PowerShell to uninstall OneDrive, and all my files saved in the user/Onedrive file in my computer were lost actually their size is more than 10 GB, so they do not safe for OneDrive and I can not find them in the Recycle Bin. Please let me know How I could recover these files.I need a quick response.

:)

 

Windows 10 - OneDrive

Right click on the app and one of the properties has an option to not automatically start it. Uncheck, restart the computer, and it should stop. If you want to go another step further, find the OneDrive app in the start menu, right click on it and uninstall.

If that is still insufficient, there is a batch uninstaller for OneDrive available online. I can copy the code here if you need it.

 

Uninstall Photo app by using Powershell command

Hi Lorraine,

Thank you for posting your response.

I apologize for the miscommunication. Follow the steps below and check if that helps.

• 
  1. Open the Start menu, type Windows PowerShell in the search bar.
  
  2. Right click on the Windows PowerShell and select Run as administrator.
  
  3. Enter the below command to uninstall the Photo app.
  
  • 
    get-appxpackage *Microsoft.Windows.Photos* | remove-appxpackage ( check the spacing)
    

After performing the above steps, install the Photo app from the Windows store.

Hope this information is helpful. Please do let us know if you need further assistance, we’ll be glad to assist you.

Thanks

 

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.