Bridge CS6 Old Problem

[DenThomp54]

There is an old problem with the Export Panel in Bridge CS6 from several years ago that has never been properly fixed.  It first happened back Oct 30, 2017 where the Export Panel disappeared.  There was a KB issued that fixed it.  Well fixed it until Nov 9, 2021 any way.  Any date after and including Nov 9, 2021 and the panel does not show up.  You can change the system time to Nov 8, 2021 and the panel appears and works just fine.  Changing the system time is the only method, but the problem is then it shows the files created on Nov 8, 2021. 

I realize there are probably not many that still use CS6, but it is very handy for those of us that do.  I currently use Dr Brown's Image Processor Pro which works, but takes a long time to run. 

Somewhere there is a setting where Bridge or the Export Panel itself reads the current time which determines whether the panel works or not.  The only part I care about getting restored is where you export to hard drive.  Is there a place in the registry or somewhere that the "expiration date" of the Export Panel be set to way in the future?  Any help or thoughts are appreciated.

Windows 7 Pro

[creative explorer]

@DenThomp54 Adobe did that on purpose. But besides saying that, try this work-around, but it may mess everything else up though....change the system clock?!

[DenThomp54]

Yes I know that Adobe did it on purpose.  Best I remember it was something about the license for Photoshop.com.  The original KB fix pushed the usable date from Oct 30, 2017 to Nov 8, 2021.   The only service I use in the panel is the Export to Harddrive and there should be no expiration date on that.  Changing the system clock works, but like said it changes the create time of the image to that date. 

About all I shoot now is my 2 grandson'd football games so will continue to use Dr Brown's Image Processor Pro even if it takes a while.

I can understand a license issue with the other services except the Export to Hard Drive which should work regardless of the date.  I also understand CS6 is an old version and not many out here probably still use it so Adobe has no reason to fix it.