Either Files Corrupted (run Recovery) Or New Record Was Just Added Ubs

[Suyay Escarsega]

SoI've been through the ringer on this, and realised some of the mistakes I made that got me here, but I'm casting this out to see if anyone may have had this experience and been able to salvage anything.

Using a Canon Vixia HF R800, I have files recorded on a Gigastone 128GB microSD card (I know, I know.) It worked on two previous projects, but halfway through one day of shooting, the files seem to have stopped recording correctly or something. I've got a day and half of video files, all with appropriate sizes, but they just have a Quicktime logo. Neither QT Player nor Preview will open them; VLC will open them, and "play" them, but even though there's a status bar, there's no audio or video, and any attempt to convert/stream outputs a kb-size file that's clearly not correct. I bought "Stellar Video Repair" and it's done nothing. A friend of mine built a droplet encoder a while back, and it's not doing anything either.

It's not the end of the world if I can't get these working (unless the client wants to reshoot, but these were the wide camera) but I'm frustrated as to why they won't go. Obviously there's data there, but the file is either not closed or not opened correctly. I have two other folders that are full of these files, but the attached picture shows that first day of footage where something must have happened in the middle of the day, because the files recorded before that on this card are fine.

It's not the end of the world if I can't get these working (unless the client wants to reshoot, but these were the wide camera) but I'm frustrated as to why they won't go. Obviously there's data there, but the file is either not closed or not openers correctly. I have two other folders that are full of these files, but the attached picture shows that first day of footage where something must have happened in the middle of the day, because the files recorded before that on this card are fine.

You're asking us to tell you what you want to hear. Unfortunately, it probably wouldn't be the truth. It is what it is, and the fact that you've "been through the [w]ringer" and learned your lesson isn't going to make those corrupted files readable.

Waddizzle is one of the more knowledgeable and respected members of this forum. Maybe he can help you, and maybe he can't. But announcing that you don't want to hear what he has to say hardly advances the ball.

I know. Just wanted to let the OP know not to bother with the manufacturer. They do not support their own products. He complained about not getting the answer the was looking for. What was the question? He never asked one.

I have a business critical Excel .xlsb file, that I have been updating/using for years (it contains about 20 sheets, and a lot of VBA code - none of which runs on opening).

Yesterday, the file refused to open on 2 different work PCs, both running the same, fully updated version of Excel from an Office 365 E3 business subscription. Whilst I thought this one file may be corrupt, I have used this file for many years, with many older versions on the file saved (some of which have not been used/opened for years) - and Excel was suddenly unable to open these versions either!? When trying to open the file, Excel would simply freeze for a bit, then close with no error messages. Opening Excel in safe mode made no difference, same issue. Further info on this led me to believe the problem was with the latest version of Excel as:

- NB I could NOT open the .xlsb file in Office 365 via the browser, I got an error message saying it needed to be viewed in the desktop (which of course didn't work either)

So there is something in this file (and previous versions) that the latest version of Excel/Excel online does not like. NB other .xlsb files I have so far seem fine.

This looks very similar to another user's issues, reported in Jan 2020 (which appears unresolved):

-workbook-xlsb-crashes-on-new-computer-and-latest-...

Can anyone shed any light? I now have a working .xlsm file - but I was only able to do this as I had a laptop with a different version of Excel on - if this wasn't the case then I could have been scuppered. And it makes me wary of using .xlsb files full-stop for now!

There are several possible reasons why Excel crashes when opening an .xlsb file, such as corrupted cache, outdated software, incompatible add-ins, conditional formatting, antivirus interference, or system issues.

You can also use a third-party tool to repair your .xlsb file, such as Stellar Repair for Excel or Kernel for Excel Repair. These tools can scan your file and recover data from damaged worksheets. Have not used these tools myself, but are recommended by some, so without guarantee.

Hi, did you ever get this resolved? I seem to have a similar problem where my .xslb file immediately closing when opening with no error message. Excel then does a repair and it works. But after a while making some macro changes, it happens again. I have tried removing all macros and reloading. Same problem after a while. I am on Windows 10, Office 360 16.0.16501.20074 64 bit.

@Duwat13 Sorry no. I was able to convert the file to .xlsm and all was fine. It did take a bit of sorting, but if you are able to open the file occasionally then I'd do this. For me, the only real advantage to a .xlsb file was smaller file size, but not much of an advantage if it doesn't work....!

I tried it several times in a situation like the one below and it works.

- My Excel is a very complex form of VBA, functions and automation in every area even for several external files (also files accessed with autogenerated name related to data in sheets which isn't possible as M$oft said - yes it is possible)

- I have such a habit to check after saving whether the file continues to open (Microsoft software in most cases is very defective and unprofessional compared to Apple)

- one day I open the main file and what do I see - crash without warning, totally nothing helped, neither cache nor reinstallation completely nothing. The file seemed to be damaged

- Another habit is always making a backup before opening the file for further work (usually adding next version number)

- renaming the corrupted file to another file - I open and it works! Excel has not crashed. I just change file name!

- back to the exact previous name - Excel crash! Vvery professional amateur problems in m$ but predictable

- rename the corrupted file again - I open and it works, no crash

- just to be sure, I return to the previous version of the name, again crash, when I duplicate this file and it already has the note "- Copy" ... copy also crash

- I delete the copy because there is no point

- I rename the original file to anything else - the result - it opens, no crash! exactly as before...

- after opening it saves via Save As... under the name I use in automation (the same one which I found out my file is damaged!). I close everything including Excel

- I open the newly saved file with the option Save as... - and it works! no crash :)

The question is what kind of garbage Excel professional programmers include to saving for themselves, and probably their teams of programmers don't even know what kind of mess they are making, how to fix it, so they ignore it.

I have noticed this many times whether in Word, PowerPoint and especially Excel re-writing a document clears or deletes some information (in Excel its really a lot!). I don't know what kind but in this particular situation it helps more than 3 times with different files.

This is an age-old problem of Windows, a very amateurish and failed system written by amateurs. They just copy ideas without knowing how to do it right. It's just a shame that such a very successful - the only (!) - M$oft product started from Lotus, today Excel has such defects and problems. This type of situation never happened on the version for Mac OS X Excel 365 and to buy for not much money. Does the benefit of Apple's brilliant, extremely stable and secure system help?

Its been my experience that Office 64 bit has serious defects, and back in 2011 or so they published on their developer website no intention of fixing the known issue causing your file to automatically close. It has to to with VISUAL BASIC. They released office with a 32 bit VB in it, despite being 64 bit office. Bug #1. They also have an unwanted Book1.xlsx that the save process will automatically create, and it is unneeded and causes the error. The VB code gets saved correctly in the xlsm file, then it adds the unwanted hidden file in error. This goes way back to Office 1998, then they thought having one file hidden that would contain all your macros was a good idea. They still have snippets of code in office that they cannot fix or locate that is trying to still save this hidden file. This is then causing your machine to open the xlsm file today, and it acts like there is an error in the file. There are no errors with your file. Just OPEN EXCEL first, a blank workbook, then click FILE OPEN and browse to your file, then in the dialogue where it sayd OPEN inthe lower right, click the tiny down errors, and use Open and Repair. It will open the file file and get rid of the unwanted file that windows adds as a brazen defect of windows .

3a8082e126