Ctrl+O behavior in Office 2013

When using Word, Excel, PPT 2013. The CTRL+O shortcut does not launch the Open dialog box for me. Instead, the File (Alt+F) screen appears. Why is this?

That is the "new & improved" method. MS is trying to encourage / push people into using skydrive.
Normally, I'd say just create a macro and over-ride the default action. But I have not been able to find the right command yet to open that dialog directly.

Similar Messages

Office 2013 simply refuses to update templates

Hi All,
Was wondering if you could help as i'm really getting thin on ideas now.
I've been working with Azure RMS for a couple of weeks with no problem but all of a sudden I can't get Office 2013 to update the custom templates I've been creating on multiple devices.
I've created custom templates before that have refreshed in Office perfectly but new ones simply will not download. As far as I'm aware everything is set as it should be in terms of the template is published and my user account is within the scope
of users who can use the template.
I have installed the RMS sharing app on my Win 8.1 machine and when right clicking a file to complete an in place protect the most up to date templates are present but whilst working directly within Word or Excel etc the templates are out of date.
I've tried all sorts of combinations of deleting the templates folder in: %AppData%\Local\Microsoft\MSIPC\Templates and deleting the LastUpdateTime dword, signing out of office and signing in again but nothing I try seems to help.
Does anyone have any ideas of what I could try?
Thanks in advance!

While this feature (departmental templates) is in Preview, Office applications don't recognize these templates, by default. From
https://technet.microsoft.com/en-us/library/dn642472.aspx#BKMK_HowToConfigureCustomTemplates, see step 8 and the behavior you're seeing:
Not all applications can support departmental templates. To do so, the application must first authenticate with the RMS service before downloading the templates. If the authentication process does not occur, by default, none of the departmental templates
are downloaded.
There is a script that you can run (see the Note) for this to work with Office applications during the Preview period. We were hoping to get the script on the Download Center, but it's currently on the Connect site. If you have problems accessing it,
email [email protected]

Office 2013: 10 Best Features You Should Know About

The new Office 2013 has some key updates that, while aren’t quite as dramatic as theWindows 8 from Windows 7change, still have some pretty cool features for mobile and desktop. Office 2013, will ship sometime next year at prices that have not been announced
yet. Check out the top 10 features:
Going Mobile. Microsoft has geared the new software towards a more mobile-friendly audience, allowing users to interact more
efficiently on mobile and tablets including finger and stylus controls that may help to spur Office’s migration to mobile devices. Another decidedly mobile move is Office Home and Student 2013 RT, which includes Word, Excel, PowerPoint, and OneNote, will come
with ARM-based Windows 8 devices including Microsoft Surface .
In The Cloud. Microsoft’s SkyDrive cloud service is being positioned to play a key role in Office users’ daily computing
lives. Office 2013 will save your documents to SkyDrive by default, enabling you to access files from multiple devices, including a smartphone and tablet. When you sign into Office from another device, your personalized settings and recently used files
are already there for you. The new Office is available as a cloud-based subscription too. Office 365 is now also available for home-based users as well as businesses. Subscribers will get automatic upgrades, additional SkyDrive storage, multiple installs for
several users, and added perks such as international calls via Skype.
Finger and Stylus. Office 2013 embraces touch and pen input. The touch and stylus features are geared towards smartphones and
tablets, as well as multi-touch laptops. The touch features are the same as users are accustomed to on their smartphones and tablets; swipe a finger across the screen to turn a page, pinch and zoom to read documents, and write with a finger or stylus.
Metro Style. Office 2013 conforms to Microsoft’s “Metro” look that’s pervasive across the software developers latest mobile
apps. The Office Ribbon in Word 2013 has a flatter look than its predecessor in Word 2010.
PDF’s in Word. You can now edit PDF files in Word 2013 (yay!). Simply open a PDF as you would any other document. Word maintains
the formatting of the file which is fully editable. You can insert pictures and videos from online sites such as YouTube and Facebook as well. And readers can watch video clips from inside your document.
Excel. Excel offers some useful upgrades including new templates for budgets, calendars, forms, and reports. The new Quick
Analysis Lens lets you convert data to a chart or table in a couple of steps. Flash Fill recognizes patters in your data and automatically fills cells accordingly. For example: if you want to separate first and last names into separate columns simply begin
typing the first names in a new column, press Ctrl+E and Excel will copy the first names for you.
PowerPoint Has Gained Power. PowerPoint 2013 now sports an updated Start screen with a variety of new themes and color schemes.
The Presenter View now makes it easier to zoom in on a diagram, chart, or other detail that you want to emphasize to the audience. The Navigation Guide lets you switch slides, even move out of sequence, from a grid that you can see but your audience can’t.
Presentations can be worked on from different PCs by colleagues to create a single presentation. Comments are allowed and presentations are saved online by default to SkyDrive.
OneNote. OneNote automatically saves your notes to Skydrive, you don’t have to click “Save”, making your brainstorming sessions
readily available across multiple devices. OneNote 2013 allows you to grab screens and add them to your notebooks.
Skype Has Been Integrated. You can now integrate Skype contacts with Microsoft’s enterprise-oriented Lync communications platform
for calling and instant messaging. Office subscribers get 60 minutes of Skype international calls each month.
Going Social. Office now includes Yammer, a secure and private social network for businesses that Microsoft tentatively acquired.
Yammer integrates with SharePoint and Microsoft Dynamics, the company’s line of CRM and enterprise resource planning apps. Office 2013′s People Card tool provides detailed information about your contacts, including their status updates from Facebook and LinkedIn.

Awesome!
Thanks for sharing the greate experience here. This is a good summary of Office 2013 cool features which is definitely useful for those who want to learn about the new Office.
Thanks,
Ethan Hua CHN
TechNet Community Support

Office 2013, Mail app error with W8.1

Hi,
Was recommended to repost in here, hope someone can provide a solution.
New to this forum, have searched and not found anything in regards to my actual issue.
Problem,
When you install Office 2013 Home and Business onto Windows 8.1 either an upgrade to 8.1 or a fresh install, I've found the mail program in Control Panel won't open.
You can't call apon the program from RUN or CMD, you can't even call apon the Mail app from Program files\office 15\mlcfg.clp right click and select Open in Control Panel.
This issue has arisen with Windows 8.1.
scenario, New Dell OptiPlex 3020 & 9020, You Install Office 2013 Home & Business either OEM or the OEM Builder pack, before or after then run the Windows 8.1 upgrade from the Store, attempt to open the Mail app in Control Panel and the
Mail app ceases to respond.
Yet, you are able to open the Mail app before the upgrade.
I just did a fresh install for a customer of Windows 8.1 OEM on an ACER laptop, tested with OEM media and the OEM Builders Install package, 32x & 64x installs and both failed to open the Mail app in Control Panel.
Actually the first install I performed didn't install the Mail app icon in Control Panel at all.
The only way I've found to rectify this issue is to run a full repair from Programs in Control Panel, which takes a while to run.

Hi ATR80,
As this thread has been quiet for a while,I would like to know if the issue happend again after you solved the issue by running a full repair from Programs in Control Panel?
If the issue persists,please try the method as I mentioned above to see if it works.
Meanwhile,if you need further assistance, feel free to let me know. I will be more than happy to be of assistance.
If the suggestion is helpful, please remember to mark it as answer which can benefit others who may encounter the similar issue as yours.
If you have any concern about this behavior, you can just unpropose it.
Regards,
Kelvin Xu
TechNet Community Support

Printer driver hangs when printing with Office 2013/Windows 8 64 bit

Printer: HP Color LaserJet CM1312nfi
Printer Driver: V5.1 (up to date, downloaded from HP support website) or Generic V5.6
OS: Windows 8 Professional 64bit
When I try to print a certain Excel document with Excel 2013 and printer driver V5.1, the program hangs and needs to be terminated via task manager. This happens always with the same document, but not with all documents. The program hangs also when opening the print preview for the same document.
The same document prints fine with the generic printer driver V5.6 and with the driver that comes with Windows 8.
The same document prints fine with driver V5.1 under Windows 7 and Office 2010. The combination Windows 7/Office 2013 was not tested. The combination Windows 8/Office 2010 was also not tested.
When I try to print an empty document with Word 2013 and generic printer driver V5.6, the program hangs and needs to be terminated via task manager.
My conclusion is that the HP printer drivers have a problem with either Windows 8 or Office 2013 or a combination of both.
The printer driver that comes with Windows 8 and is automatically installed is useful as a temporary workaround, but it lacks certain options, e.g. manual duplex.
On request, I am ready to send the Excel document by e-mail for verification of the problem.
Any help or suggestions will be very much appreciated.
Thanks in advance,
Uli
This question was solved.
View Solution.

From what you describe you are having issues printing from MS Office. Have you had trouble printing from other resources on your computer (e.g. from the internet or another program)? The first thing I am going to suggest is that we start by uninstalling and reinstalling the printer from the resources available online.
First if you use a USB cord, make sure to remove it (this is important). Do not plug it back in until the software directs you to. Then go through the Devices and Printers, Programs and Features and Device Manager folders and insure that all copies, files, and programs related to the printer are removed. Then as directed, restart the computer.
In the START menu type "%temp%" and press ENTER. Here I want you to press Ctrl+A and hit DELETE. Some of the files will not allow you to delete them, skip those files and delete the majority that allows it.
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3562006&lang=en&cc=us...
Install that and let me know the result!
Have a great day!

Office 2013 with Visio and Project Error - Package manifest is invalid

In July I successfully created an App-V install of Office 2013 VL using the ODT. This week I decided to try just doing Visio as we don't install it or Project on all systems. I used my same customconfig.xml and just changed the ProPlusVolume to VisioProVolume
and changed the source path. Everything downloaded and packaged fine. I was able to import into SCCM just fine and create a deployment to my test collection. However when I run the install out of Software Center I get (as part of a much longer error) the message
in AppEnforce.log that the package manifest is invalid. Thinking that maybe I had to include Office as long with Visio I tried packaing all three items but still get the same error. Has anyone else seen this behavior and/or ideas how to fix it? Can I sequence
just Visio or just Project? I'm including my config.xml just in case I've got something wrong with it that I haven't caught. Thanks
<Configuration>
<Add SourcePath="<networkpath>\Microsoft\AppVOffice2013\Sept\" OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
<Product ID="ProjectProVolume">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Hy. I'm having the same problema.
I'm trying to create na app-v package (v.5 SP2) of Office 2013.
I downloaded the Office Deployment Tool for Click-to-Run from here:
http://www.microsoft.com/en-us/download/details.aspx?id=36778
I installed it into C:\Office2013pck shared that folder as
\\APPVMANAGER\Office2013 and mapped as Z:\.
I changed the configuration.xml file to:
<Configuration>
<Add OfficeClientEdition="32" >
<Product ID="ProPlusVolume">
<Language ID="en-us" />
</Product>
<Product ID="VisioProVolume">
<Language ID="en-us" />
</Product>
</Add>
</Configuration>
Then I ran in na elevated cmd:
>Z:
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /download
\\APPV-CL-WIN7DEF\Office2013\configuration.xml
and
>\\APPV-CL-WIN7DEF\Office2013\setup.exe /packager
\\APPV-CL-WIN7DEF\Office2013\configuration.xml
\\APPV-CL-WIN7DEF\Office2013\Appv
Everything seemed to work fine.
The creted folder had Office\Data\15.0.4649.1001 folder (I guessed this is a version number)
When I tried to add the package to App-V Server (in the Console) I get the following error:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I tryied to publish it from powershell, getting the same error message agalluci image post shows.
From the Event Log I got this additional information:
There was a problem retrieving the requested package \\APPVMANAGER\AppVpck\Office\VisioProVolume_ProPlusVolume_en-us_x86.appv for import. Error message: Unspecified error
Element '{http://schemas.microsoft.com/appv/2010/manifest}UsedKnownFolders' is unexpected according to content model of parent element '{http://schemas.microsoft.com/appx/2010/manifest}Package'.
I haven't found any indication of which file is the manifest app-v file.
I also haven't found any .xml with the "UsedKnownFolders" tag (I changed the .appv package extension to .zip and explored some of the files).
I tryied creating a package for 32 and 64 bits, only office, office and visio, and office visio and project running Windos 7 and Windows 2012.
Thanks in advance for any help.

Office 2013 Installer - Fails with No Errors

Hello,
I ran into issues on two different Windows 8 (64-bit) machines today, both with Office 2013 Pro Plus (32-bit) installed. I could not get the installer to come up to add a module (or make any other changes).
On one of the PCs, I tried running the Fixit to remove Office, since the option of the "Online Repair" was not accessible, (installer would not start). Fixit removed Office, but after a reboot, it still would not run the office installer, even
with Office 2013 completely gone.
Things I tried:
- Disabled anti-virus (windows defender)
- Run with elevated privileges (I'm a domain admin and UAC is off, but just to be safe)
- Removed skydrive
- Cleaned out temp directory
- Scanned for registry errors (none)
- Re-downloaded the installer DVD
- Made sure no pending windows update
- Reboots (lots of times, definitely after the uninstall)
- Checked the install log in %temp%, this is what I get:
2013/08/12 13:51:14:263::[2848] PERF: TickCount=1295931 Name=OBootStrapper::Run Description=Begin function
2013/08/12 13:51:14:264::[2848] Operating System version: 6.2.9200 . Platform ID: 2
2013/08/12 13:51:14:264::[2848] Running 32-bit setup on a 64-bit operating system.
2013/08/12 13:51:14:264::[2848] Command line: "F:\SETUP.EXE"
2013/08/12 13:51:14:264::[2848] No command line arguments given
2013/08/12 13:51:14:513::[2848] Verify file signature in "F:\SETUP.EXE"
2013/08/12 13:51:14:562::[2848] F:\SETUP.EXE is trusted.
2013/08/12 13:51:14:562::[2848] Verify file signature in "F:\proplus.ww\OSETUP.DLL"
2013/08/12 13:51:14:598::[2848] F:\proplus.ww\OSETUP.DLL is trusted.
2013/08/12 13:51:14:612::[2848] Using setup controller dll at [F:\proplus.ww\OSETUP.DLL].
2013/08/12 13:51:14:612::[2848] PERF: TickCount=1296274 Name=OBootStrapper::Run Description=Calling RunSetup
This is almost identical to what I see on the other PC, except with different drive letters.
THERE ARE NO ERROR MESSAGES - no popup, no installer dialog - nothing, which makes it really hard to troubleshoot. And it's happening on both Windows 8 machines that have had Office 2013 installed. I am so frustrated right now after wasting half of today
troubleshooting this.
Any thoughts?

Hi
Let’s follow these steps:
Make sure you have end the tasks of setup.exe and integratedoffice.exe.
   1. Press the Ctrl + Alt+ Delete key -> Click on Task Manager to open.
   2. Under Processes tab -> Select setup.exe -> Click on End Process.
    3. Under Processes tab -> Select integratedoffice.exe -> Click on End Process.
  Restart the computer in Clean Boot and install Office 2013. Follow the steps:
       http://support.microsoft.com/kb/929135
   Note: After you have finished troubleshooting in clean boot, ensure you restart the computer in normal mode.
In addition, you can also refer to the following link to try more methods:
http://support.microsoft.com/kb/2822317/en-us
Regards

Unable to install 32 bit version of Office 2013

We had several computers deployed with the 64 bit version of Office 2013. Due to some unforeseen compatibility issues, we needed to remove the 64 bit version and then install the 32 bit version. While we have been able to remove the 64 bit version,
we are not able to install the 32 bit version. After we click setup.exe, We simply see the Office 2013 splash page that mentions "Please wait while setup prepares the necessary files" and then it disappears. Nothing in the event log either.
Any idea what is going on and how to resolve this?

Hi,
Do you mind telling us which category of Event viewer have you checked?
Most of the setup error log may be stored in Setup category, and some in Application category.
If there are some error logs, please upload, they'll help us to troubleshoot this issue.
Then, this issue also may be due to the remain of Office 2013 64bit. I recommend we remove it manually and clean the registry key:
==========
Method 1
Open C:\Program Files\Microsoft Office 15\root\integration\
Delete all C2RManifest*.xml files in that folder.
Open an elevated command prompt. Tap on Windows, enter cmd, right-click on the result and select run as administrator from the menu.
Type cd "C:\Program files\Microsoft Office 15\root\integration".
Type integrator.exe /U.
To remove the Office 2013 preview scheduled tasks run the following commands.
Type schtasks.exe /delete /tn "FF_INTEGRATEDstreamSchedule"
Type schtasks.exe /delete /tn "FF_INTEGRATEDUPDATEDETECTION"
Type schtasks.exe /delete /tn "FF_INTEGRATEDOffice 15 Subscription Heartbeat"
Keep the command prompt open.
Open the Task Manager with Ctrl-Shift-Esc.
Click on the Process tab and kill the following processes: integratedoffice.exe,
appvshnotify.exe, firstrun.exe and setup*.exe.
Type sc delete OfficeSvc at the command prompt.
Open Windows Explorer and delete the Microsoft Office 15 folder
Open %ProgramData%\Microsoft and delete the ClickToRun folder
Open %ProgramData%\Microsoft\office and delete the
FFPackageLocker file
Press Windows, type regedit and hit enter to open the Registry editor
Delete the following Registry keys.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppVISV
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Office 15 - ProfessionalRetail - en-us
Note that the name of the last Registry key depends on the installed version of Office.
Delete Office 2013 start menu shortcuts
Open %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs and delete the Office 2013 folder
Go to the command prompt and run one of the following commands:
If you are running an x86 version of Office 2013 and an x64 operating system run the following command:
MsiExec.exe /X{50150000-008F-0000-1000-0000000FF1CE}
If you are running an x86 version of Office 2013 and an x86 operating system run the following command:
MsiExec.exe /X{50150000-007E-0000-0000-0000000FF1CE}
If you are running an x64 version of Office 2013 and and x64 operating system run the following command:
MsiExec.exe /X{50150000-008C-0000-1000-0000000FF1CE}
Run the following command afterwards: MsiExec.exe /X{00150000-008C-0000-0000-0000000FF1CE}
Method 2
Open the %windir%\Installer folder. Make sure you can view Hidden files and folders on your system
Select View, then Choose Details
Select Subject, type 340 in the width of the column and click ok. This may take several minutes before subjects appear.
Select View > Sort by > Subject
Locate all .msi files that have Microsoft Office 2013 product names and uninstall them.
Use Windows-R to open a run box
Enter services.msc and hit the enter key
Locate Office Source Engine and right-click the service and select
Stop from the context menu.
Open the %CommonProgramFiles%\Microsoft Shared folder or
%CommonProgramFiles(x86)%\Microsoft Shared on a 64-bit operating system
Delete the folders Office15 and Source Engine from the folder list.
Open the %ProgramFiles%\Microsoft Office folder or %ProgramFiles(x86)%\Microsoft Office on 64-bit systems
Delete the Office15 folder.
Open the MSOCache folder on the root of the hard drive
Open the All Users folder and delete every folder that contains 0FF1CE} in the name
Open the folder %appdata%\microsoft\templates
Delete the following files Normal.dotm and Welcome to Word.dotx
Open the folder %appdata%\microsoft\document building blocks
Delete the building blocks.dotx file
Press Windows-r, type regedit and hit enter
Open the following Registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0
Delete the following Registry keys if you are running a 32-bit version of Windows.
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\*0FF1CE}-*
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*0FF1CE*
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Upgrade Codes\*F01FEC
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\*F01FEC
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose
HKEY_CLASSES_ROOT\Installer\Features\*F01FEC
HKEY_CLASSES_ROOT\Installer\Products\*F01FEC
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\*F01FEC
HKEY_CLASSES_ROOT\Installer\Win32Assemblies\*Office15*
Delete the following Registry keys if you are running a 64-bit version of Windows
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Delivery\SourceEngine\Downloads\*0FF1CE}-*
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*0FF1CE*
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose
HKEY_CLASSES_ROOT\Installer\Features\*F01FEC
HKEY_CLASSES_ROOT\Installer\Products\*F01FEC
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\*F01FEC
HKEY_CLASSES_ROOT\Installer\Win32Asemblies\*Office15*
On a 32-bit version of Windows, open the following Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
On a 64-bit version of Windows, open the following Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
Select File > Export, type UninstallKey01 and select Save.
Under the uninstall key determine the subkey that has the following values:
Name: UninstallString
Data: file_name path\Office Setup Controller\Setup.exe path
Delete the keys that match the data and repeat the process until all keys have been processed.
====
On the other hand, the installation source also may be a factor, please try to change one and test.
https://products.office.com/en-us/download-back-up-restore-microsoft-office-products?legRedir=true&CorrelationId=9398947d-5b49-4e53-a203-0ef5ff858293
Hope it's helpful.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

SCCM 2012 R2 Office 2013 deploiement 64 bit and 32 bit versions

We have some
Windows 7 64bit os with office 2013 32 bit
also
Windows 7 32bit os with office 2013 32 bit
We need to deploy office 2013 32 bit all over with sccm 2012 r2
what's the best way for the deployment
we also want to be sure to keep all user data for outlook. we don't want to loose that
can I install a 32 bit office and in the setup /admin use uninstall and everything will work

setup.exe /admin is the tool to use when customizing the deployment of Office; especially when deploying through SCCM.
The way I saved user profile data is to set it to Use Existing Profile under Outlook Profile of setup /admin
Yes, I have the default setup behavior box checked so it removes all previous Office version applications.

Office 2013 click-to-run does not honor deselecting 'Make Outlook the default program' checkbox

We use an email client other than Microsoft Outlook (let's say Thunderbird)
Thunderbird is set as the default mail client for the machine (HKLM\Software\Clients\Mail\(default) set appropriately)
Occasionally, we launch Outlook (but absolutely do not want it as the default mail client for the machine). About 30 seconds after launching Outlook, we see that the Windows default mail client changes to Microsoft Outlook.The 'Make Outlook the default
program for E-mail, Contacts, and Calendar' checkbox in File->Options is disabled.
Further investigation with ProcMon indicates that a SYSTEM service called integrator.exe starts up about 30 seconds after we launch Outlook. This service changes the HKLM\Software\Clients\Mail\(default) registry key to be Microsoft Outlook.
We have tested with multiple non-Outlook email clients, and the behavior is always the same.
This only happens on click-to-run installs of Office 2013. Regular installs of Office 2013 do not have the problem. Older versions of Outlook do not have the problem.
What can we do to get Outlook to honor the 'Make Outlook the default program' setting?

Kapaal -
Thanks for your reply. Your blog post would certainly work if this was just a user-mode app that was making the change, but that's not the case with Office 2013.
The integrator.exe process that is making the change is part of Microsoft's Click-to-Run system. It runs as a service with local system access, and thus would have full access to the key. I might be able to lock it down by creating a second system
admin account and playing games with it - but that will make it very difficult to actually change the value when I want it do be changed, and I really shouldn't have to be doing workarounds to prevent Office itself from doing this.
- Kevin

Office 2013 Professional Plus configures each time you start

I have a problem that has been well documented for Office 2010.
I have just installed Office 2013 as an upgrade from Office 2010 and every time I open an Office 2013 application I get the following message:
'Please wait while windows configures Microsoft Office Professional Plus 2013".
I have tried to follow the solutions provided for Office 2010, particularly Microsoft article ID 2528748; Method 1 did not solve the problem and using Method 2 the Fix It was not applicable and as I am using Windows 7, I was unsure how to manually apply
the fix.
Has anyone else experienced this problem and found a solution.
Regards
As an update, I did manually apply Method 2 but it still did not solve the problem. I considered doing a System Restore back to Office 2010 and found there were resore points created to 'uninstall' and 'reinstall' Office 2013 which corresponded to 'configures'
message.

Below is the answer I got from Max Meng (a forum moderator) when I posted a new question (it looks like I am going to have to completely uninstall and reinstall to see if that fixes it, but maybe this will help someone else). The thread this comes
from is:
http://social.technet.microsoft.com/Forums/en-US/officeitpro/thread/105fb8c6-c974-42c1-b783-c5e6f31d6d17
I thought restoring all security settings to default values was interesting. I noticed that I had some issues in my registry that prevented the SecEdit command from completing properly, but even when I had cleared them up, I still haven't fixed the
problem. I am also checking into possible interaction with Dragon Naturally Speaking (does anyone else who has the problem have that installed?). Here is what Max told me:
Not sure if you have tried to repair your Office, if no, please try to repair your Office as a quick fix.
If that doesn't work, try to fix it with the following methods:
Method 1:
Open an elevated Command Prompt, type the following command, and then pressENTER:
secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
Method 2:
Try start Office in safe mode, see if this problem will still persists. (Press and hold the CTRL key, and then click the Office program to start it in safe mode.)
If the problem does not occur in safe mode, this issue might be related to third-party add-ins. Disable the add-ins and start Office to see whether the problem continues to occur.
If the problem continues to occur in safe mode, we recommend that you uninstall Office and then install it. To do this, read the following Microsoft knowledge base article:
http://support.microsoft.com/kb/2739501

Office 2013 on RDS, icon appears and dissapears

Hello.
We have multiforest enviroment. Forest A ( there are accounts ) and forest B where are APPV mgmt and RDS servers. Users from Forest A login to RDS servers in forest B with no problem. We have domain group (say FS USERS) in forest B that includes users account
from forest A and we publish MS Office for this group.
Every other application published for domain group "FS USERS" work, but MS Office 2013 not. When logging, Office icons for 8seconds appears and after that disappears ( i think when office intergration task run ).
When i publish office for group in domain B and
accounts that comes from domain B, office works.
Can anyone recommend
what to do, what check?
I enable debug logging but nothing special found.
Thanks, Jan

Hello.Yes, jump to fully supported model.
I write before, we try it, 1 ODT per machine like we are using for any other packages.
We end with error :
The virtual application 'C:\Windows\Explorer.EXE' could not be started because the App-V Subsystem 'Virtual Shell' could not be initialized. {error: 0xC701525-0x54F}
The virtual application 'C:\Windows\Explorer.EXE' could not be started because the App-V Subsystem 'Registry Staging' could not be initialized. {error: 0x78A00A0A-0xA0005}
The main and annoying effect is when user logon, there popup dialog:
Runtime Error!
Program: c:\windows\explorer.exe
R6030
- CRT not initialized
I must run explorer.exe from task manager manualy ( CTRL+ALT+END) and after that office appears
There is empty RUNVIRTUAL entry in registry.
We have latest APPv subsystem. Appv-SP3, resp. 5.0.10107.0
Server is on clean install, W2008R2Ent
It doesn't matter if user is form forest or local domain, have redirected %APPDATA% or not.
Office Deployment Toolkit 15.0.4623.1001
Jan
CONFIGURATION
Id                        : 1
SetByGroupPolicy          : False
Name                      : APPV
URL                       : http://cenzored:8001
GlobalRefreshEnabled      : True
GlobalRefreshOnLogon      : True
GlobalRefreshInterval     : 0
GlobalRefreshIntervalUnit : Day
UserRefreshEnabled        : True
UserRefreshOnLogon        : True
UserRefreshInterval       : 0
UserRefreshIntervalUnit   : Day
Name             : PackageInstallationRoot
Value            : %programdata%\App-V
SetByGroupPolicy : False
Name             : PackageSourceRoot
Value            :
SetByGroupPolicy : False
Name             : LocationProvider
Value            :
SetByGroupPolicy : False
Name             : AutoLoad
Value            : 1
SetByGroupPolicy : False
Name             : EnablePackageScripts
Value            : 1
SetByGroupPolicy : True
Name             : ReestablishmentInterval
Value            : 5
SetByGroupPolicy : False
Name             : ReestablishmentRetries
Value            : 3
SetByGroupPolicy : False
Name             : CertFilterForClientSsl
Value            : LOCAL_MACHINE\MY\1.3.6.1.5.5.7.3.2
SetByGroupPolicy : False
Name             : SupportBranchCache
Value            : 0
SetByGroupPolicy : False
Name             : VerifyCertificateRevocationList
Value            : 1
SetByGroupPolicy : False
Name             : SharedContentStoreMode
Value            : 0
SetByGroupPolicy : False
Name             : MigrationMode
Value            : 0
SetByGroupPolicy : False
Name             : RoamingFileExclusions
Value            :
SetByGroupPolicy : False
Name             : RoamingRegistryExclusions
Value            : SOFTWARE\CLASSES
SetByGroupPolicy : False
Name             : AllowHighCostLaunch
Value            : 0
SetByGroupPolicy : False
Name             : RequirePublishAsAdmin
Value            : 0
SetByGroupPolicy : False
Name             : IntegrationRootUser
Value            : %LOCALAPPDATA%\Microsoft\AppV\Client\Integration
SetByGroupPolicy : False
Name             : IntegrationRootGlobal
Value            : %ALLUSERSPROFILE%\Microsoft\AppV\Client\Integration
SetByGroupPolicy : False
Name             : VirtualizableExtensions
Value            : exe,com,bat,cmd,vbs,ps1,cpl,jar,wsf,wsh,msc
SetByGroupPolicy : False
Name             : IgnoreLocationProvider
Value            : 0
SetByGroupPolicy : False
Name             : ReportingEnabled
Value            : 0
SetByGroupPolicy : False
Name             : ReportingStartTime
Value            :
SetByGroupPolicy : False
Name             : ReportingRandomDelay
Value            :
SetByGroupPolicy : False
Name             : ReportingInterval
Value            :
SetByGroupPolicy : False
Name             : ReportingServerURL
Value            :
SetByGroupPolicy : False
Name             : ReportingDataCacheLimit
Value            :
SetByGroupPolicy : False
Name             : ReportingDataBlockSize
Value            :
SetByGroupPolicy : False
Name             : ExperienceImprovementOptIn
Value            : 0
SetByGroupPolicy : False
Name             : EnablePublishingRefreshUI
Value            : 0
SetByGroupPolicy : False
Name             : ProcessesUsingVirtualComponents
Value            : {%SystemRoot%\explorer.exe, %ProgramFiles%\Internet Explorer\iexplore.exe, %ProgramFiles(x86)%\Inter
                   net Explorer\iexplore.exe}
SetByGroupPolicy : False
Name             : EnableDynamicVirtualization
Value            : 1
SetByGroupPolicy : False

Excel COM object calls break with Office 2013 upgrade on 64-bit OS?

Out of the 1000+ computers in the company mine is the only one running 64-bit windows 7. I have noticed that when i try to run a small DLL i created to convert Excel files to Tab Delimited files it is crashing only on my computer.
I have debugged the source code and found that there is no real exception being thrown except a popup does appear in the background stating "We're sorry, but Excel has run into an error that is preventing it from working correctly. Excel will need to
be closed as a result. Would you like us to repair now? [Repair Now][Help][Close]"
If i open excel via the main application this same popup comes up and when i click repair excel closes. when re-opened Excel re-activates and then works fine.
here is a sample of my (VERY simple) code which has worked for years on office 2007 with 64-bit OS:
Dim excelPath As String = "C:\test.xlsx"
Try
objXL = CreateObject("Excel.Application")
With objXL.Application
.displayalerts = False
.Visible = False
.workbooks.Open(excelPath)
.Workbooks(ExcelFileName).SaveAs(csvPath & csvFileName, Excel.XlFileFormat.xlCurrentPlatformText, , , , , Excel.XlSaveAsAccessMode.xlNoChange, , , , , )
.workbooks(csvFileName).Close(csvPath & csvFileName, savechanges:=True)
End With
Catch ex2 As Exception
Throw ex2
Finally
objXL.Quit()
objXL = Nothing
End Try
I have isolated the exact line that is causing the exception to be thrown...
.Visible = False
Why would hiding the Excel UI cause an error of "We're sorry, but Excel has run into an error that is preventing it from working correctly" to be displayed?
If i remark out this line then the application seems to work properly for me...

That I do not know. Do you have another machine where Office 2013 is installed, and where you can test? It could be system configuration issue, could be a change in the application behavior or a difference between 32-bit and 64-bit. You are updating
at least a couple of generations of software and now running in a 64-bit environment so there is always the potential for changes in behavior and software defects.
Unfortunately, I do not have Office 2013 64-bit installed so I cannot test this scenario.
You could also try posting to the
Excel for Developers forum to see if anyone has encountered the same issue when using Excel automation.
Paul ~~~~ Microsoft MVP (Visual Basic)

Don't use Backstage option in Office 2013

The new backstage view in Office 2010 was great for a business environment. It showed a long list of recent workbooks and recent folders and so, even working on many workbooks, there was a very good chance that one, or at worst two, clicks would get
me to the workbook I needed to work on.
In 2013 this is a whole lot harder as you only see either recent workbooks or recent folders and the lists take up more space so fewer files/folders are visible. Also Skydrive, which I doubt if many businesses would use, is far too prominent and cannot
be removed (?) The list of recent files in the menu bar is too narrow so it is often not possible to distinguish between files with similar names without hovering over and waiting!
Anyway, there is an option, (File/Options/Save) "Don't show the Backstage when opening or saving files". I have tried this option in Word and Excel and it doesn't seem to make any difference, at all. Am I missing something?
Oh BTW as IT manager I am recommending that we do not move to Office 2013. Backstage and color theme are the killers.

1st, well, I just counted the number of the Recent Workbooks on Office 2010 and Office 2013, and the number of Office 2010 is 3 more than Office 2013. When Office 2010 has 21 recent workbooks, Office 2013 has 18 on my 19" screen (1280*1024 resolution).
If that matters, try click the Send a Frown button in any Office applications to send your feedback to the Product team, :)
2nd, the width of the Recent Workbooks in Office 2013 are almost the same as Office 2010, I mean, if you can see the full name in Office 2010, you should also be able to see the full name in Office 2013.
From the above, it seems you might have mixed up the Start screen with the Recent Workbooks menu (which, BTW, also shows 16 recent workbooks).
To turn off the Start screen, uncheck the option "Show the Start screen when this application starts" in Excel or other Office applications.
3rd, the option "Don't show the Backstage when opening or saving files" does make a difference, try figure it out by compare the save or open behavior between turn it on and off.
4th, for the "color theme" issue, now we have "White", "Light Gray" and "Dark Gray", and our product team is also aware of the feedback from our cutomers, let's hope we can get more themes from the future release.
5th, for the SkyDrive, yes, I haven't found any option to remove it. Unless you are interested in creating your own customized backstage view. If so, I'd suggest you to visit the Office for Developers forums for further discussion:
http://social.msdn.microsoft.com/Forums/en-US/category/officedev
Max Meng
TechNet Community Support

SharePoint Workspace 2010 still installed after upgrade to Office 2013

I'm working on a deployment of Office 2013 in a corporate environment. Using the OCT, I've customized a package which is working well on machines that don't have previous version of Office installed. However, many of the existing machines currently
have Office 2010. After executing the Office 2013 package, we're noticing that while the upgrade works, SharePoint Workspace 2010 and the Office 2010 Tools still exist in the Start -> Programs menu. I also see Office 2010 in Add/Remove programs
(along with the new Office 2013). The OCT is specifically set to uninstall previous editions of Office during the upgrade (which is the default behavior).
I'll seen a couple of other posts like this on the forum, but unfortunately no answers. How can I *completely* uninstall Office 2010 (including SharePoint Workspace 2010 and the Office 2010 tools) during the upgrade to Office 2013? This
corporation doesn't need SharePoint Workspace 2010; my guess is that it was included by default with the Office 2010 package that they rolled out in the past.
Thanks!

Hi,
By default, the uninstall option in Office Customization Tool (OCT) will not remove SharePoint Workspace 2010 as SharePoint Workspace is no longer include in Office 2013.
Try to create a separate Office 2010 .msp file, set Microsoft SharePoint Workspace and Office Tools to "Not Available" and deploy it
prior to the installation of Office 2013.
Or you can do an Uninstall upgrade. Basically, use the /uninstall [ProductID] command-line option to uninstall Office 2010 from the user's computer first and then after that is finished, install Office 2013.
Here is a great example of how to perform an uninstall-upgrade for enterprise deployments :
http://blogs.technet.com/b/odsupport/archive/2011/04/06/how-to-perform-an-uninstall-upgrade-to-office-2010.aspx (Note, the steps are wrriten for Office 2010, but it holds good for Office 2013.)
More reference:
http://technet.microsoft.com/en-us/library/cc178956.aspx#BKMK_uninstall
http://technet.microsoft.com/en-us/library/ff602181.aspx
Hope this helps.
Thanks,
Ethan Hua CHN
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Ctrl+O behavior in Office 2013

Similar Messages

Maybe you are looking for