Windows 10: Excel startup pop-up

I intentionally deleted some reundant files from my hard drive. But now every time I start Excel a screen pops up saying "Sorry we couldn't find xxxx is it possible it was moved renamed or deleted". I don't need the file, it is just annoying that the screen keeps popping up. How do I disable the pop-up or sever the link?

:)

 

Can't get GPU-Z to start with Windows 8.1 startup

I'm not sure how to do that. Could you list the steps for a noob?

 

Help needed with Excel Attendance Sheet

You use the Data tab, Data validation facility to do this.

If you want a coherent explanation then look in Excel Help. Here's the relevant extract from Excel 2007 Help. Excel 2007 Help - Data Validation.pdf

My example:
- I have written them in what seems to me to be the order of easiest explanation.
- You'd actually set them up in the reverse order - step 3, step 2, step 1.

1 The result - my dropdown list. I select the cell then click on the dropdown arrow that appears next to it.




2 To set this up, select the whole column [or individual cells] where you want the dropdown to appear then click on the Data tab then the Data validation control. You need to
- select In-cell dropdown
- set the Allow entry to List
- in Source, enter the worksheet name & cell range where you have written the allowable entries - you will generally want to use absolute cell references such as those shown [$ in a cell address means absolute and will not vary as you copy the formula all the way down your column - look this up if you are not familiar with it because it needs a bit of getting used to].




3 Write out the list of allowable entries that will appear in your dropdown list.




Job done.

Denis

 

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.