File Searcher By Owner Now Open Source

File Searcher by Owner, the number one utility for finding files and folders owned by a particular user or group, is now open source and available on its GitHub repo.
File Searcher by Owner, the number one utility for finding files and folders owned by a particular user or group, is now open source and available on its GitHub repo.
I recently wrote a PowerShell script for Windows that will check if a program or update is installed and, if not, download it using BITS in low priority, verify the download hash, and then install it and copy the verbose log to a central repository. The example is for the current latest Microsoft Surface Pro 7 firmware, but it can be adapted for just about any installer.
Read on for the script code...
This popular screensaver utility has been updated! Two versions have been released:
1.6.3 (2020-06-15) - The final version that runs natively on older operating systems, requiring either .NET 2 or 3.5.
2.0.3 (2020-06-15) - Includes all the updates from version 1.6.3 and has been converted to run natively on newer operating systems.
After many years, we've released the next version of File Searcher by Owner!
File Searcher by Owner is the number one utility for finding files and folders owned by a particular user or group.
Download File Searcher by Owner 2.0
Much of the code has been rewritten and there are a number of new features in this release:
Version 2.0.2.0 (2020-05-15)
Known Issues
Upcoming Features
OK. Here is how I deployed the AlwaysOn VPN in device tunnel (rather than user tunnel) using PowerShell. Continue on for the steps...
Did you know that you can, with one easy PowerShell command, extract all 3rd-party Windows drivers from a computer to a folder? It uses the DISM module and is built into newer versions of Windows.
All the details and switches for this are available from Microsoft's PowerShell Documentation at https://docs.microsoft.com/en-us/powershell/module/dism/export-windowsdriver
Update (2017-06-27): We release a patched version (1.5.4) that implements a couple other minor updates and changes.
We've finally released the next version of Screensaver Operations.
Screensaver Operations is an application for Microsoft Windows systems that allows you to perform configurable actions after a computer has been left idle for a specified amount of time (e.g., log off, shut down, run a process).
Download Screensaver Operations 1.5
There are a lot of new bug fixes and a couple features in the latest release:
Thanks for the suggestions everyone. What’s in the pipeline? This:
UPDATE (2013-04-02): 1.4 was completed last week; we just are working getting the proper installer file(s) working. Expect it out this week.
UPDATE (2013-04-05): 1.4 has been released. ADM files are in the works still. Note that following Microsoft's installations standards has forced us to create separate 32-bit and 64-bit MSI installers. Both versions should upgrade the previous 1.3 install without issues (assuming you previously used the MSI to install).
Dear admins! I know we've been missing with updates for a while, but we hope to get things rolling again soon! To that end, I wanted to update everyone on the latest beta version of Screensaver Operations. This beta release is primarily marked by the ability to natively run on both 32-bit and 64-bit Windows, as well as some feature requests.
Download Screensaver Operations Beta 1.4-b now in our forums!
Screensaver Operations is an application for Microsoft Windows systems that allows you to perform configurable actions after a computer has been left idle for a specified amount of time (e.g., log off, shut down).
Some viruses now are messing with your file associations making it hard to open programs, such as your Web browser so that you can download and install an anti-mailware program, or even open the cleaner application itself. It's usually simple to remove the changes made when in a registry editor, but since Regedit.exe and other editors are executable files, you can't easily open them either!
Below is a registry fix that I have found useful to have on hand to easily reset the .EXE file association back to it's normal state so that you are no longer prevented from running programs.
Repair EXE Registration.reg
Windows Registry Editor Version 5.00
[-HKEY_CURRENT_USER\Software\Classes\.exe]
[-HKEY_CURRENT_USER\Software\Classes\secfile]
[-HKEY_CLASSES_ROOT\secfile]
[-HKEY_CLASSES_ROOT\.exe\shell\open\command]
[HKEY_CLASSES_ROOT\exefile\shell\open\command]
@="\"%1\" %*"
[HKEY_CLASSES_ROOT\.exe]
@="exefile"
"Content Type"="application/x-msdownload"
Importing this registry data file will remove any custom edits that any malware makes to your .EXE file associations in the HKCU area and then sets the file association open command back to normal. From there you should be able to open your malware cleaning tools.
We recommend that you copy the registry data file to a local disk on your computer prior to running due to the fact that newer versions of Windows will often by default not allow you to import a .REG file if you run it from a network share.