Hi Zac,
Below I repeat the workaround I mentioned already in this forum in January. Since I followed the procedure below, Outlook works fine for me. No more trouble.
But it's strange that Windows doesnt repair the bug at all. No action so far.
This is how I did it:
Hi all,
After studying numerous posts on numerous forums on the web regarding this ridiculous bug (where is your patch, finally, Microsoft?????) I found out that none of the solutions worked for me. But I think I did find an experimental workaround myself: I de-activated the CALENDAR tab and now access my calender through the todo-pane that is visible in my email/contact/note views. So the same todo/task panes that others recommend to close, is MY stepping stone.
This is how I did it:
- I started OUTLOOK.EXE through the RUN command, with flags /cleanprofile /cleanviews /resettodobar (as mentioned in earlier posts - thanks!) to have a clean version
- Through the Tools > Options > Other > To-Do-Bar I activated the todo-bar, with two rows of two calendar months (I have enough space on a wide screen laptop) - and including tasks, no problem.
- In the menu on the bottom left of Outlook I used the option 'show fewer buttons' to de-activate the CALENDAR button - that tab seems to be the object that triggers the trouble, in my case at least. If it's not there you cannot (ab)use it.
- I restarted Outlook and could work normally.
- When in email/contact/note view i can access any calendar date through the todo-bar - and switch back - without anyproblem (so far!)
What NOT works:
- In Tools > Options > Other > Advanced Options I selected: startup in this folder: CALENDAR. I should NOT have done that: my mouse could not even access the Outlook window, bumped against the Outlook borders. Nor could I click any command. Don't ask me how I got rid of this frustrating loop - but finally I managed to select MAIL again as my startup folder. (By the way: this simple startup preference should not be hidden far in the 'advanced, other options' - but in a first 'general' tab! Microsoft: change it!)
I am curious if (being a simple computer user, not a whizz-senior, this workaround works for others as well as it does for me. Mail me at
wimyogya@gmail.com with your comment - I dont access these forums, usually.
But first of all I wait for the day Microsoft comes with a real solution for this apparently essential bug in their software. Hurry up, please!
WimYogya
Dutch senior in Indonesia