Solid Edge Hide assembly .cfg files in Windows Explorer

If you work with a lot of Solid Edge assembly files contained within a single folder then the view of the files in Windows Explorer may become unnecessarily cluttered with assembly configuration (.cfg) files:

How to hide these Solid Edge .cfg files in Windows Explorer so that the Explorer view is less cluttered? 

Solid Edge out-of-the-box does not provide any functionality to hide assembly configuration (.cfg) files within Windows Explorer.  However, by applying a basic Windows operating system command we can quickly and easily hide the .cfg files so that the .cfg files do not display in Windows Explorer.

By default this is what a end user would see in Windows Explorer when viewing a folder containing Solid Edge assembly files such as the Solid Edge Training folder.  Note the list of .cfg files being displayed:

To change this behaviour we can use the DOS command line utility attrib.exe.  To use attrib.exe:

Open a Command Prompt window.

In the Command Prompt enter the following command line:

attrib +h "<path to the folder containing our Solid Edge files>\*.cfg" /s

For example, using the Solid Edge Training folder:

After applying the above command line, all the .cfg files in the specified folder and its sub-folders are now set to hidden.

Continuing with the example of the Solid Edge Training folder location, with "Hidden Items" turned on in Windows Explorer the .cfg file icons are now dimmed indicating that these .cfg files are now marked hidden:

With "Hidden Items" turned off in Windows Explorer the .cfg files are no longer visible to the user:

This marking of .cfg files as hidden also carries over to the Windows Search results.  For example searching for files called "carrier" in the Solid Edge Training folder will only return the .asm files and the .cfg files will not be listed in the search results unless "Hidden Items" is explicitly turned on:

By implementing a small script either running as a service or as a scheduled task you can then periodically have the script running to update all new.cfg files to then be set to hidden, thereby permanently resolving the user's dilemma of .cfg file overload.

If at anytime, you wish to revert the .cfg files to no longer being marked as hidden simply run the attrib command again but instead use the "-h" switch in place of the "+h" switch.

For more on the attib.exe command see the following Microsoft documentation:

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/attrib