>Do you have a reference for where Nikon have acknowledged this >"bug" (other than your telephone converstaion)? >I've not been able to find any trace of it online. > >I can't understand the tech telling you the D banks >"contain Nikon specifications", because the user is >able to change any and all settings in these banks, just like >in banks A, B or C.
A short chronology: I called Nikon USA when I first saw the problem yesterday. The tech I spoke with told me to switch to D in both the Shooting and the Custom Settings banks. This fix worked and the grayed-out items (Lock Mirror Up For Cleaning and Dust Off ref Photo) immediately became available again. I fooled around with the banks a bit and found that I only needed to switch to D for the Custom settings bank. I told this to the tech and she tried it on her own D800 and it worked. The tech at Nikon then said Nikon is aware of the issue and told me that the reason why Custom Settings bank D works is because this bank contains some hidden camera specifications that the other banks do not. I agree with you regarding this explanation and think it sounds like a bunch of horse manure.
I then e-mailed the author David Busch (new D800/E book) and he emailed me back saying that he had experienced the same thing and found the 'D bank' solution allowed access to the menu items in question. He also said that he wrote to Nikon Professional Services and heard back from their top service manager who had heard of the problem and was interested in the solution that Busch described. That was 6-months ago!
I have found on-line references to this bug with a variety of suggested fixes but not including the one given to me by Nikon as described above.
Here's just one of them: forums.dpreview.com/forums/thread/3212362
Please call Nikon yourself. I'd be mighty interested to find out what they'll say to you. I trust that you will report your conversation with them accurately.
This bug does not appear to occur on an out-of-the-box D800/E - at least not in my case. This is probably why not everyone is reporting it. It's only after many settings have been altered by the user that it becomes apparent. I have no clue as to which of these setting changes cause the problem.