Salesforce

Shortcuts mixed together in Windows 10 Start menu

« Go Back

Information

 
TitleShortcuts mixed together in Windows 10 Start menu
URL Nameshortcuts-mixed-together-in-windows-10-start-menu
Article Number000159488
EnvironmentProduct: OpenEdge
Version: 11.7
OS: Windows 10, Windows Server 2012 R2
Question/Problem Description
When 32-bit and 64-bit OpenEdge are both installed on Windows 10, and the default shortcut group folders "Progress\OpenEdge 11.7(32-bit)" and "Progress\OpenEdge (64-bit)" are retained, the "OpenEdge (nn-bit)" subfolders are not created. This causes 32-bit and 64-bit shortcuts with the same names to be mixed together under the "Progress" folder:

Progress Win10 Start menu folder with duplicate shortcut names
Steps to Reproduce
Clarifying Information
Problem does not occur on Windows 7
Error Message
Defect NumberDefect PSC00339996, PSC00356755
Enhancement Number
Cause
The exact cause is not known at this time.
Resolution
None at this time. Until the fix is available, use one of the workarounds below.
Workaround
Consider one of the following workarounds:
  • Specify a distinct name for the shortcut folder in each version. Each name should specify a single folder with no subfolder underneath (do not specify two folder names separated by a backslash).
 
  • The following Powershell workaround can be used to resolve this shortcut issue where multiple verisons of OpenEdge installed on one of these systems.    It will rename the files in the start menu/metro screen:
$ProgressStartMenuDir="C:\ProgramData\Microsoft\windows\Start
Menu\Programs\progress"
$OEreleases=(get-childitem $ProgressStartMenuDir |  where {$_.Attributes -eq
'Directory'}).name
foreach  ($Eachrelease in $OEreleases)

    $Version=$Eachrelease.replace('OpenEdge','')
     #write-host  $Version
     cd  $ProgressStartMenuDir/$Eachrelease        
    $files=get-childitem *.lnk -rec | where {$_.Name -Notlike "*$Version*"} 
    foreach ($file in $files)  
    {  
           $newfileName = $file.Name.Replace(".lnk", "$Version.lnk")   
           rename-item $file -newname $newfileName; 
           #write-host  $file
    } 
           
}

 
Instructions to run the code above:
1) Create a text file that contains the code above, and name the file with the
.PS1 file extension
2) Run the newly created  .PS1 script with Administrator privileges

Important Note: Since the workaround renames existing files to include verison information, the standard OpenEdge uninstall will not remove these shortcuts. On an uninstall after applying the work around, the shortcuts must be deleted manually from “C:\ProgramData\Microsoft\windows\Start Menu\Programs\progress\<Uninstalled _OE_Release>".
Notes
Defect PSC00356755 was closed as a duplicate of PSC00339996.

References to Other Documentation

Progress Articles

 Progress OpenEdge 11.7 Readme
 
Keyword Phrase
Last Modified Date11/20/2020 7:16 AM

Powered by