No, i mean with nscb verify function, if it gives an exception you can do a raw extraction and verify the nca independently too. Though that seems to say that the nca header magic is "0000" instead of PFS0, if it's a messed up header it won't be able to verify either, you can see that in hex though:Will re download the update and see what's up
A nsp begins like this:
With 50465330, that translates as PFS0