Windows 10: Shortcut to xlsm file not working correctly

I have a shortcut to an Excel xlsm file which used to open it in Excel directly. Excel is the default for this extension. Recently the system pops up a verification window, which is a nuisance. Using Office 16, 3/07/19.

Here's the shortcut:





And here's the response:





How can I convince Windows to accept the default automatically?

:)

 

Need to find an unconventinally filed C: xxxx..xlsm

Hi Jay,

You can search for the file in your C: drive by following these steps:

1. Press Windows key + E on your keyboard to open Windows Explorer.
2. On the left-hand pane, click This PC and select C: (or where you want to look for a file).
3. On the upper-right hand of the window, you should see a text box with the text
   Search Windows C: (or what is the current directory of your folder).
4. Type in the text box the name of the file you want to search for. You can also search for the extension of the file. Type .xlsm and that will show all files that have that kind of extension.

Update me if you've found the file.

 

Screensaver shortcut

I did this"
Search Results

I would suggest you to try the following steps and check if that helps.

• Go to the folder C:\Windows\System32 and sort by file type.
• Look for the screensaver file type (.scr).
• Find the file scrnsave.scr(you can choose any of the screensavers).
• Right click and select send to>desktop (create shortcut). The shortcut on my attachment, but when i click on it my screen goes off and on and nothing else.

 

Creating Shortcuts with Batch File

Threw a program together quick for you. It is attached with source in the other. Use it in place of your VBScript.

It supports:
CreateShortcut [save shortcut] [path to run]
CreateShortcut [save shortcut] [path to run] [icon index]
CreateShortcut [save shortcut] [path to run] [icon file]
CreateShortcut [save shortcut] [path to run] [icon file] [icon index]

If "icon index" is missing, it assumes 0. If "icon file" is missing it assumes "path to run." It doesn't presently support arguments to be added to the shortcut nor modifying the working directory (always assumes same directory as "path to run").

Requires .NET Framework 4.0 to run. Will run natively on 32-bit and 64-bit versions of Windows.