Jump to content
CCleaner Community Forums
Sign in to follow this  
Dukmiester2

Recent Files in Office 2003 programs not cleaned

Recommended Posts

I am trying to figure out how to get rid of the recent files listed near the bottom of

the FILE menu in Office 2003 programs, Microsoft Office Document Imaging in particular.

 

post-25395-1229471680_thumb.jpg

 

I have found it necessary to keep ALL the files I EVER opened

using Microsoft Office Document Imaging because of a problem

that develops with the FILE menu after my PC crashes or locks up for any reason.

 

Just the nature of my rig, and I have gotten used to it.

 

It is a pain having to keep all those files, If I delete any after a

crash or lock up, the FILE menu in Microsoft Office Document Imaging

then causes an error and the program closes. If I restore those

deleted files, the FILE menu in Microsoft Office Document Imaging

works again!

 

My thinking is if I can "erase the memory" of Microsoft Office Document Imaging,

then maybe my little problem will be cured and I can finally delete all these

old files without causing Microsoft Office Document Imaging to have a

coronary.

 

Any way to get CCleaner to wipe those recent files so the Office

2003 programs won't look for them?

 

As a test, the same thing shows up in WORD, although when I delete

files, it doesn't crash, it just no longer has said files in the bottom of the

FILE menu.

I have tried using CCleaner and it doesn't seem to be doing what I need.

I REALLY want to get rid of these recent files permanently,

any help will be greatly appreciated.

 

Thanks for reading,

bye for now...

post-25395-1229471680_thumb.jpg

Share this post


Link to post
Share on other sites

Hi this is a known thing and there have been recent Winapp2.ini entries created for it

 

Here are some

 

[*MS Office Picture Manager]

LangSecRef=3021

Detect=HKCU\Software\Microsoft\Office

Default=True

FileKey1=%LocalAppData%\Microsoft\OIS|OIScatalog.cag

FileKey2=%LocalAppData%\Microsoft\OIS\thumbnails|*.*

 

[*MS Office Publisher 2003]

LangSecRef=3021

Detect=HKCU\Software\Microsoft\Office\11.0\Publisher

Default=True

RegKey1=HKCU\Software\Microsoft\Office\11.0\Publisher\Recent File List

 

[**MS Office 2003 Word]

LangSecRef=3021

Detect=HKCU\Software\Microsoft\Office\11.0

Default=True

RegKey1=HKCU\Software\Microsoft\Office\11.0\Word\Data|Settings

Share this post


Link to post
Share on other sites
Hi this is a known thing and there have been recent Winapp2.ini entries created for it

 

Here are some

 

Thanks for the info. So, I guess if I understand all of this, the Winapp2.ini file is used for

"unsupported" extras for CCleaner, kind of along the lines of a Game Mod where the program

can be "modded" by users to perform additional tasks, but obviously they (the publishers)

can't support user created additions.

 

This is good news! Thanks again. If I can read through the beginner's guide, download

the Winapp2.ini and add the proper lines to it to achieve my desired results,

I'll Promptly register this software, well worth the price to get this little problem of

mine solved once and for all.

 

Thank you again for the reply :)

Share this post


Link to post
Share on other sites

Dukmiester2, I don't think I would use the term for Winapp2.ini file as "unsupported" but as User Enhanced extras for CCleaner to clean.

Share this post


Link to post
Share on other sites
Thanks for the info. So, I guess if I understand all of this, the Winapp2.ini file is used for

"unsupported" extras for CCleaner, kind of along the lines of a Game Mod where the program

can be "modded" by users to perform additional tasks, but obviously they (the publishers)

can't support user created additions.

 

This is good news! Thanks again. If I can read through the beginner's guide, download

the Winapp2.ini and add the proper lines to it to achieve my desired results,

I'll Promptly register this software, well worth the price to get this little problem of

mine solved once and for all.

 

Thank you again for the reply :)

 

Yup. I had the same problem till I found the winapp2.ini trick ;). Now, it's solved

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×