<div>
Take a look at my blog post: <a href="https://leinss.com/blog/?p=2471" rel="ugc">https://leinss.com/blog/?p=2471</a> I ran into a similar issue of shortcuts pointing to an old file server and a script to fix them to point them to the new server.
</div>

<div>
Amazing! Exactly what I was hoping to get! I added the 'Start In' ($lnk.WorkingDirectory ) portion to it. Trying to simplify the switch between x86 and x64 and vise versa. Below is an example if it detects the x64 "C:\Program Files\Google\Chrome\Application\chrome.exe" the path are updated Question: What modification can I do so it can change path to x86 if x86 Chrome is detected? ------------------------------------------------ $x86Prefix = "C:\Program Files (x86)\Google\Chrome\" $x64Prefix = "C:\Program Files\Google\Chrome\" # Script converts Chrome Path from x86 to x64 if x64 Chrome is detected. if (Test-Path -Path "C:\Program Files\Google\Chrome\Application\" ) { $searchPath = "C:\TEMP\Shortcuts\" $dryRun = $True $shell = new-object -com wscript.shell if ( $dryRun ) { &nbsp; &nbsp;write-host "Executing dry run" -foregroundcolor green -backgroundcolor black } else { &nbsp; &nbsp;write-host "Executing real run" -foregroundcolor red -backgroundcolor black } dir $searchPath -filter *.lnk -recurse | foreach { &nbsp; &nbsp;$lnk = $shell.createShortcut( $_.fullname ) &nbsp; &nbsp;$oldPath= $lnk.targetPath &nbsp; &nbsp;$oldPathStartin= $lnk.WorkingDirectory &nbsp; &nbsp;$lnkRegex = "^" + [regex]::escape( $x86Prefix ) &nbsp; &nbsp;if ( $oldPath -match $lnkRegex ) { &nbsp; &nbsp; &nbsp; $newPath = $oldPath -replace $lnkRegex, $x64Prefix &nbsp; &nbsp; &nbsp;$newPathStartin = $oldPathStartin -replace $lnkRegex, $x64Prefix &nbsp; &nbsp; &nbsp; write-host "Found: " + $_.fullname -foregroundcolor yellow -backgroundcolor black &nbsp; &nbsp; &nbsp; write-host " ReplacePath: " + $oldPath &nbsp; &nbsp; &nbsp; write-host " With: &nbsp; &nbsp;" + $newPath &nbsp; &nbsp;&nbsp; write-host " ReplaceStartin: " + $oldPathStartin &nbsp; &nbsp; &nbsp; write-host " With: &nbsp; &nbsp;" + $newPathStartin &nbsp; &nbsp; &nbsp; if ( !$dryRun ) { &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;$lnk.targetPath = $newPath &nbsp; &nbsp; &nbsp;&nbsp;&nbsp;$lnk.WorkingDirectory = $newPathStartin &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;$lnk.Save() &nbsp; &nbsp; &nbsp;&nbsp;} &nbsp; &nbsp;} } } &nbsp;
</div>

GGHC

<div>
Thanks Adam! Like your blog site. Good topics- <a href="https://leinss.com/blog/" rel="ugc">https://leinss.com/blog/</a> But Have one more head scratcher it seams Google at some point created "chrome_proxy.exe" as found in some shortcuts. Below is the output of a dry run.&nbsp; Found: &nbsp;+ C:\temp\shortcuts\Scratch Notes.lnk ReplacePath: &nbsp;+ C:\Program Files (x86)\Google\Chrome\Application\chrome_proxy.exe &nbsp;With: &nbsp; &nbsp; + C:\Program Files\Google\Chrome\Application\chrome_proxy.exe What is a slick way to always make it "..Application\chrome.exe" if it's a x64 Chrome install?? Here is the current working copy <pre><code class="code-10 nolinks" id="code-20-43320834-1">$x64Chrome = "FALSE"
$x86Chrome = "FALSE"

if (Test-Path -Path "C:\Program Files\Google\Chrome\Application\" ) {
$x64Chrome = "TRUE"
$Prefix = "C:\Program Files\Google\Chrome\"
$oldPrefix = "C:\Program Files (x86)\Google\Chrome\"
}

if ($x64Chrome -eq "False") {
$x86Chrome = "TRUE"
$Prefix = "C:\Program Files (x86)\Google\Chrome\"
$oldPrefix = "C:\Program Files\Google\Chrome\"
} 

#$searchPath = "$env:APPDATA\ClassicShell\Pinned\"
$searchPath = "c:\temp\shortcuts\"

$dryRun = $True
$shell = new-object -com wscript.shell

if ( $dryRun ) {
&nbsp; &nbsp;write-host "Executing dry run" -foregroundcolor green -backgroundcolor black
} else {
&nbsp; &nbsp;write-host "Executing real run" -foregroundcolor red -backgroundcolor black
}

dir $searchPath -filter *.lnk -recurse | foreach {
&nbsp; &nbsp;$lnk = $shell.createShortcut( $_.fullname )
&nbsp; &nbsp;$oldPath= $lnk.targetPath
&nbsp; &nbsp;$oldPathStartin= $lnk.WorkingDirectory

&nbsp; &nbsp;$lnkRegex = "^" + [regex]::escape( $oldPrefix ) 

&nbsp; &nbsp;if ( $oldPath -match $lnkRegex ) {
&nbsp; &nbsp; &nbsp; $newPath = $oldPath -replace $lnkRegex, $Prefix
&nbsp; &nbsp;&nbsp; $newPathStartin = $oldPathStartin -replace $lnkRegex, $Prefix

&nbsp; &nbsp; &nbsp; write-host "Found: " + $_.fullname -foregroundcolor yellow -backgroundcolor black
&nbsp; &nbsp; &nbsp; write-host " ReplacePath: " + $oldPath
&nbsp; &nbsp; &nbsp; write-host " With: &nbsp; &nbsp;" + $newPath
&nbsp; &nbsp;&nbsp; write-host " ReplaceStartin: " + $oldPathStartin
&nbsp; &nbsp; &nbsp; write-host " With: &nbsp; &nbsp;" + $newPathStartin

&nbsp; &nbsp; &nbsp; if ( !$dryRun ) {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;$lnk.targetPath = $newPath
&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;$lnk.WorkingDirectory = $newPathStartin
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;$lnk.Save()
&nbsp; &nbsp; &nbsp;&nbsp;}
&nbsp; &nbsp;}
}

</code></pre>
</div>

<div>
That did it! Ended up using it this way <pre><code class="code-10 nolinks" id="code-20-43320887-1">$x64Chrome = "FALSE"
$x86Chrome = "FALSE"


if (Test-Path -Path "C:\Program Files\Google\Chrome\Application\" ) {
$x64Chrome = "TRUE"
$newPrefix = "C:\Program Files\Google\Chrome\"
$oldPrefix = "C:\Program Files (x86)\Google\Chrome\"
}

if ($x64Chrome -eq "False") {
$x86Chrome = "TRUE"
$newPrefix = "C:\Program Files (x86)\Google\Chrome\"
$oldPrefix = "C:\Program Files\Google\Chrome\"
} 

if ($x64Chrome -eq "True") {
&nbsp; &nbsp;$newPath = "C:\Program Files\Google\Chrome\Application\chrome.exe"
&nbsp; &nbsp;}else {
&nbsp; &nbsp;$newPath = "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
&nbsp; &nbsp;}


</code></pre>and &nbsp;removed &nbsp; &nbsp; $newPath = $oldPath -replace $lnkRegex, $newPrefix Thanks again for all your help!
</div>

<div>
<div class="content wysiwyg-content fr-view">
We have user that have roaming shortcuts both Chrome and Office apps. They toggle between systems that have apps installed as (x86) or native 64-bit. &nbsp;This causes issue with the shortcuts. Many are Chrome apps (using --app=https://.. in the Target) -How do I programmatically change the "Target" and "Start in" to just replace the ..(x86)\ or add it back without affecting the rest of the path. - Is it possible that a script can get an inventory of the one that are ..(x86) and the one that aren't from a given path? &nbsp; &nbsp;-Possible to do it by using if Exist statements( for example if exist "C:\Program Files\Google\Chrome\ &nbsp; Replace shortcut with Open to other suggestions.&nbsp; 
</div>
</div>


We have user that have roaming shortcuts both Chrome and Office apps. They toggle between systems that have apps installed as (x86) or native 64-bit.  This causes issue with the shortcuts.
Many are Chrome apps (using --app=https://.. in the Target)
-How do I programmatically change the "Target" and "Start in" to just replace the ..(x86)\ or add it back without affecting the rest of the path.
- Is it possible that a script can get an inventory of the one that are ..(x86) and the one that aren't from a given path?
   -Possible to do it by using if Exist statements( for example if exist "C:\Program Files\Google\Chrome\   Replace shortcut with
Open to other suggestions. 

How to change a Windows shortcut's &quot;Target&quot; and &quot;Start in&quot; via script from C:\Program Files (x86)\ to Program Files\

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

A scripting language is a programming language that supports scripts, programs written for a special run-time environment that automate the execution of tasks that could alternatively be executed one-by-one by a human operator. Scripting languages are often interpreted (rather than compiled). Primitives are usually the elementary tasks or API calls, and the language allows them to be combined into more complex programs. Environments that can be automated through scripting include software applications, web pages within a web browser, the shells of operating systems (OS), embedded systems, as well as numerous games. A scripting language can be viewed as a domain-specific language for a particular environment; in the case of scripting an application, this is also known as an extension language.

How to change a Windows shortcut's &quot;Target&quot; and &quot;Start in&quot; via script from C:\Program Files (x86)\ to Program Files\

How to change a Windows shortcut's "Target" and "Start in" via script from C:\Program Files (x86)\ to Program Files\