What replaces office picture manager in office 2013?

windows live photo gallery requires 10x the clicks, starts 3 programs, and is inferior to o2k10 picture manager for quick touch-up of camera phone snaps. crop, resize, simple corrections. with windows live, one must first launch the viewer (which cannot edit, Doh!) then say edit to have it launch the pig slow and resource hog gallery app. Then, when gallery finally starts, you must go find the photo again to edit it. When you do, the tools are hidden, inconvenient, and the i am feeling lucky option for auto-touch-up is ****. trying picasa next. bad choice, microsoft.

Hey John

I tried windows live and it don't even hold a candle to office picture manager and when you try to use it downloads all photos to your computer and groups everything  and I have over 6000 photos and need to fix them on their USB drives and they need to put back picture manager because it works.

The Office Picture Manager has been a very quick and easy tool to use, built into Office and readily available no matter what machine I have to use.  I would rather not have to install 3rd party software to do what MS has made easy to do in the past.

Any word on what this app is called now and where it's hidden in the Office 2013 install?

Thanks!

Hey John,

You are correct that Office Picture Manager was removed from the suite. Inside programs such as PowerPoint and Word there are still editing tools. You also have Windows Live Photo Gallery which I feel is a much more program specific picture editing tool. Hopefully the small change does not effect your trial of the Next Microsoft Office.

Thanks for Posting!

The "not compatible" message MAY be due to 32-64 bit conflict, (but that is just a guess) ie you have 64 bit Office installed and tried to install 32 bit Picture Manager.

When you get an error, we Need the FULL and EXACT Error message text and error code (if there is one) as Diagnostic Clues

First rule of asking questions, you have to provide enough information about what you are doing so we can try to recreate the problem. If there is an error code generated, we need to see that too.

Describe the exact steps you take to create the error (so we can try to recreate it) and the resulting error. In theory that is obvious, but apparently you didn't give us enough information to provide a good answer ... <sigh>

We search various sources for the error message you give us to find possible solutions. So we need the exact error message text, we can't find paraphrased error messages.

http://ask-leo.com/can_i_avoid_retyping_error_messages_when_i_need_to_report_them.html

This link describes a shortcut to capture the FULL and EXACT error message text in a message box. As of Win 2000, <CTL><C> captures error text from most(some?) dialog boxes. Report it back here by pasting the text into a reply, or typing the full message if you can't copy it.

Win7 & Win8 Problem Steps Recorder - PSR

http://windows.microsoft.com/en-CA/windows7/How-do-I-use-Problem-Steps-Recorder

http://www.maximumpc.com/article/how-tos/how_use_windows_7_problem_steps_recorder_make_easy_pc_guides 

http://msdn.microsoft.com/en-us/library/dd371782%28v=vs.85%29.aspx

http://www.7tutorials.com/easy-troubleshooting-and-problem-solving-problem-steps-recorder 

https://www.youtube.com/watch?v=z6EgLm3-XcQ

http://blogs.msdn.com/b/patricka/archive/2010/01/04/using-the-secret-windows-7-problem-step-recorder-to-create-step-by-step-screenshot-documents.aspx

Please use the Problem Steps Recorder to capture what you are doing so we have more details to work with. Either copy and paste the recorded steps into the forum or upload the zip file to Skydrive and give us a link to the zip file

Solving problems unique to a machine can be an arduous task for both the end-user and the help desk. That’s why Win7 introduces the Problem Steps Recorder, a screen-capture tool that allows the end-user to record the problems they’re having step-by-step. If the problem is repeatable, the recorder will capture what you do in text form.

It’s as simple as hitting “record” then adding in comments as needed. A HTML-based file is converted to a .ZIP folder, which is easily passed on to the help desk.  The program is accessible from the Control Panel under “Record steps to reproduce a problem” or run psr.exe from Explorer.

Upload result to a file share site and post the link back here.

Trouble shooting Problems Installing Office 2003/2007/2010/2013 (Verbose logging)

Enable verbose logging before collecting the log files.

1.      Click on Start -> All Programs

2.      Accessories -> RUN

3.      Type reg add HKLM\SOFTWARE\Microsoft\ClickToRun\OverRide /v LogLevel /t REG_DWORD /d 3

4.      Click on OK.

Now try to install Microsoft Office 2013 to get the error message so that the log files get created.

Provide the complete error log present in the ‘Temp’ folder to help you better.

Follow the steps below to access the ‘Temp’ folder.

1.      Click on Start -> All Programs

2.      Accessories -> RUN

3.      Type %temp%  -> Click on OK

Following are the log files that may be present in the %windir%\temp folder (c2r is for Click to Run):Bootstrapper*.log

1.      c2r_*.log

2.      C2RIntegrator*.log

3.      Firefly*.log

4.      Integratedoffice.exe_c2r*.log

5.      Interceptor*.log

6.      *.exe.log

7.      *_c2rdll*

MSI, "Normal", installations the log files will look like MSI****.LOG