Get-Windows10LockScreenWallpapers uses by default one of the three methods below to determine the source path, where the Windows Spotlight lock screen wallpapers are stored locally:
\SOFTWARE\Microsoft\Windows\CurrentVersion\Lock Screen\Creative\LandscapeAssetPath"HKEY_CURRENT_USER: "\SOFTWARE\Microsoft\Windows\CurrentVersion\Lock Screen\Creative\LandscapeAssetPath"$($env:LOCALAPPDATA)\Packages\Microsoft.Windows.ContentDelivery*\LocalState\Assets" path, which on most Windows 10 machines would most likely point to the "\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets" directory$env:windir\Web\Screen directory)
- The methods are tested in an ascending order and selected as the primary (only) method, if deemed to be valid. By adding the -Include parameter to the command launching Get-Windows10LockScreenWallpapers the third method of wallpaper searching will be enabled, so that Get-Windows10LockScreenWallpapers will also look to the current lock screen hive, even if the first method (registry) or the second method (estimation) was selected as the primary method for searching the available local lock screen wallpapers.
-IncludeHive parameter to the command launching Get-Windows10LockScreenWallpapers the third method of wallpaper searching will be enabled, so that Get-Windows10LockScreenWallpapers will also look to the current lock screen hive, even if the first method (registry) or the second method (estimation) was selected as the primary method for searching the available local lock screen wallpapers.
Get-Windows10LockScreenWallpapers uses the inbuilt Get-FileHash cmdlet to calculate SHA256 hash values of the files for determining, whether a wallpaper already exists in the -Output folder or a portrait picture in the -Subfolder directory. By default Get-Windows10LockScreenWallpapers writes the landscape files to "$($env:USERPROFILE)\Pictures\Wallpapers"(, which is the default -Output directory), and the portrait pictures are placed in a subfolder called "Vertical" inside the folder specified with the -Output parameter. The primary save location ("destination") may be set with the -Output parameter, and the name of the subfolder may be changed with the -Subfolder parameter – the former accepts a full path as a value, and the latter just a plain directory name.
@@ -153,8 +153,8 @@
-Includewith an alias -IncludeCurrentLockScreenBackgroundHive. If the -Include parameter is used in the command launching Get-Windows10LockScreenWallpapers, the third method of wallpaper searching will be enabled, so that Get-Windows10LockScreenWallpapers will also look to the current lock screen hive, even if the first method (registry) or the second method (estimation) was selected as the primary method for searching the available local lock screen wallpapers. Usually this will add a directory called '$env:windir\Web\Screen' to the list of source paths to be queried for new images. Please note that the items inside the current lock screen hive may be of varying file extension type, including mostly .jpg and .png pictures.
-IncludeHivewith aliases -IncludeCurrentLockScreenBackgroundHive and -Include. If the -IncludeHive parameter is used in the command launching Get-Windows10LockScreenWallpapers, the third method of wallpaper searching will be enabled, so that Get-Windows10LockScreenWallpapers will also look to the current lock screen hive, even if the first method (registry) or the second method (estimation) was selected as the primary method for searching the available local lock screen wallpapers. Usually this will add a directory called '$env:windir\Web\Screen' to the list of source paths to be queried for new images. Please note that the items inside the current lock screen hive may be of varying file extension type, including mostly .jpg and .png pictures.
@@ -285,7 +285,7 @@
./Get-Windows10LockScreenWallpapers -Output C:\Users\Dropbox\ -Subfolder dc01 -Include-Include parameter was used, the third method of wallpaper searching will be used in any case, which usually means that that the contents of '$env:windir\Web\Screen' are also used as a source. Compares the SHA256 hash values of the found files against the hash values found in the "C:\Users\Dropbox\" and "C:\Users\Dropbox\dc01" folders to determine, whether any new files are present or not. All new landscape images are then copied to the "C:\Users\Dropbox\" folder, and all the new portrait images are copied to the "C:\Users\Dropbox\dc01" subfolder. Since the path or the subfolder name doesn't contain any space characters, they don't need to be enveloped with quotation marks. Furthermore, the word -Output may be left out from the command as well, because -Output values are read automatically from the first parameter position.-IncludeHive parameter was used, the third method of wallpaper searching will be used in any case, which usually means that that the contents of '$env:windir\Web\Screen' are also used as a source. Compares the SHA256 hash values of the found files against the hash values found in the "C:\Users\Dropbox\" and "C:\Users\Dropbox\dc01" folders to determine, whether any new files are present or not. All new landscape images are then copied to the "C:\Users\Dropbox\" folder, and all the new portrait images are copied to the "C:\Users\Dropbox\dc01" subfolder. Since the path or the subfolder name doesn't contain any space characters, they don't need to be enveloped with quotation marks. Furthermore, the word -Output may be left out from the command as well, because -Output values are read automatically from the first parameter position.
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine
@@ -318,10 +318,10 @@
Undefined, the effective execution policy is Restricted, which is the default execution policy. This parameter will not alter or remove the ("master") execution policy that is set with a Group Policy setting.Turn on Script Execution" overrides the execution policies set in Windows PowerShell in all scopes. To find this ("master") setting, please, for example, open the Group Policy Editor (gpedit.msc) and navigate to Computer Configuration → Administrative Templates → Windows Components → Windows PowerShell.Turn on Script Execution" overrides the execution policies set in Windows PowerShell in all scopes. To find this ("master") setting, please, for example, open the Local Group Policy Editor (gpedit.msc) and navigate to Computer Configuration → Administrative Templates → Windows Components → Windows PowerShell.gpedit.msc) setting "Turn on Script Execution":gpedit.msc) is not available in any Home or Starter editions of Windows.
| Group Policy Setting Value | +Group Policy Setting "Turn on Script Execution" |
PowerShell Equivalent (concerning all scopes) |