First, I don't think you should expect a public beta for PP2. Why? Well, the public beta for PP1 was for the specific purpose of banging on the patch for the file corruption issue identified late last year. I don't think there would have been a public beta except for that. Second, there are people who are still (almost 6 months later) running the beta of PP1, I suspect because they didn't realize (even though it was clearly laid out in the release notes and here in the forums) that you have to uninstall the beta to get the RTM bits.
As for a workaround, there are enough strange dependencies that there's no workaround I can think of easier than deciding if you're going to plug your computer in for a backup tonight, and shutting it down completely if you're not. I have several laptops that all display this issue, and that's what I've resorted to.
Good points about PP1, you're probably right. I was under the impression that all beta bits from MS had an hardcoded expiration date, but apparently some do not. I didn't realize such a small omission could turn into a maintenance nightmare so quickly...
Thanks for the suggested workaround. I'm not prepared to give up on hibernation for the laptop, keeping the same session opened for days is too much of a time saver. Unless Lara can suggest something better, I prefer to live without the convenience of automated laptop backups than without the convenience of hibernation. (I probably have these priorities backwards.)
I have to say, though: I am amazed that this issue has persisted for so long, especially since it was identified during the beta period. Before Lara's post, the problem was still
unconfirmed! I realize not every bug can be fixed before a release and some hard choices must be made (I am a software developer myself), but this would have been a
perfect candidate for PP1.
I'd love to hear the real story, but I'm sure it isn't something to be shared publicly :)
Cheers,
Ben.
