Hi @Balangan1970,
Thank you again for your detailed report and for your patience throughout this process. I’ve spent time researching the issue and testing multiple approaches, including those commonly recommended in the community. After careful investigation, it appears that this is a limitation introduced in Excel Version 2509, specifically when working with Pivot Tables that include a SUM subtotal and are saved in format..xlsb
The issue seems to stem from how Excel 2509 handles the internal structure of Pivot Tables in binary workbooks. When reopening the file, Excel fails to properly read the Pivot Table metadata, resulting in either a deletion of the Pivot Table or a failure to open the file. This behavior does not occur in Version 2508 or earlier, which confirms that the problem is specific to the newer build.
Although I’ve made every effort to find a workaround, I regret to inform you that the results on my end are consistent with yours, the Pivot Table is removed when reopening the file in Excel 2509. I truly wish I could offer a direct fix, but at this time, the best course of action is to report the issue to Microsoft so it can be addressed in a future update.
If you are an admin, you can report this issue directly to Microsoft so they can investigate and potentially include it in a future update.

Alternatively, you can send feedback directly from Excel:
File > Feedback
Include a brief description and attach the affected file if possible.
To avoid disruption to your work, I recommend reverting to Excel Version 2508. Here's how:
Open Command Prompt as Administrator.
Run the following command: cd %programfiles%\Common Files\Microsoft Shared\ClickToRun officec2rclient.exe /update user updatetoversion=16.0.16227.20258
Wait for the rollback to complete, then restart Excel.
For full instructions, you can refer to Microsoft’s official guide here: How to revert to an earlier version of Office
I also want to thank you for your clear and thorough description, it has been extremely helpful in reproducing and understanding the issue. In fact, I’ve seen a few similar reports from other users, which suggests this may be affecting more people.
If you found this information helpful and feel it clarifies the issue, you might consider marking this as the Accepted Answer. This will help other users discover the workaround more easily and encourage more feedback to Microsoft, which can accelerate a fix.
I’ll continue to monitor this issue and update this thread if any new developments or fixes become available.
If you have any further questions or updates, feel free to reach out.
Best regards,
Liora