Using classic Outlook for Windows in business environments
Solved problem by deleting NEW version. System now recognizes CLASSIC as default.
Thanks for responses
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am using Outlook classic (win 11, 64 bit),
When I click apps it shows Outlook new as default.
How do I make Outlook classic as default?
Using classic Outlook for Windows in business environments
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Solved problem by deleting NEW version. System now recognizes CLASSIC as default.
Thanks for responses
Thanks for reply
My problem is that I have outlook classic installed but the system apps show NEW one as default.
I have an extension to share pages which I need to use my installed classic.
Any way to reset this easily?
Hi, jfirstlast
Thanks for your response and glad to hear that everything works well for now and please click Yes to help us improve the support experience and help others with similar concerns.
Best Regards,
Cece | Microsoft Community Support Specialist
Dear jfirstlast
Thanks for your further clarification!
If you don't want to fall back to an older version using a run script, in New Outlook, if you have seen the toggle switch, you can select the toggle switch to switch back to Classic Outlook and New Outlook will close. For more details, please refer to Run new Outlook and classic Outlook side-by-side - Microsoft Support
Please feel free to share with me on any developments about this issue!
Best regards
Cece-MSFT | Microsoft Community Support Specialist
Dear jfirstlast
Welcome to Microsoft Community.
I realize that you want to revert back to Classic Outlook for Windows. You can use PowerShell code to achieve this goal.
Here are details:
#Define the current username
$username = $env:USERNAME
# Define the folder path to operate on
$folderPath = "C:\Users\YOURUSERNAME\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\Migration"
# Define the path of the file to delete
$fileToDelete = "$folderPath\settings.json"
# 1. Delete the specified file (if it exists)
if (Test-Path -Path $fileToDelete) {
Remove-Item -Path $fileToDelete -Force
Write-Host "File $fileToDelete has been deleted."
} else {
Write-Host "File $fileToDelete does not exist."
}
# Get the username of the current logged-in user
$currentUser = [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
# 2. Get the Access Control List (ACL) of the folder
$acl = Get-Acl -Path $folderPath
# Define a new access rule to deny write access for the current user
$denyWriteRule = New-Object System.Security.AccessControl.FileSystemAccessRule($currentUser, "Write", "Deny")
# Add the deny write access rule to the folder's ACL
$acl.AddAccessRule($denyWriteRule)
# Apply the modified ACL to the folder
Set-Acl -Path $folderPath -AclObject $acl
# Output the result of the operation
Write-Host "Write access denied for $currentUser on $folderPath"
The code performs two actions. You can also perform these actions manually if your code does not perform them correctly.
Sincerely hope that everything can work well!
Best regards
Cece-MSFT | Microsoft Community Support Specialist