You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would have simply guessed that the same p-code compiler was carried forward from 2019, but if that were true, I would have expected the version to be AF 00 like the other recent 32-bit versions instead of the version number that has been associated with 64-bit.
By way of letting you know that O365/Office 2021 is absent from the list of valid Office versions in your switch construct, I thought I would ask if you've encountered this too and learned anything about it?
The text was updated successfully, but these errors were encountered:
I noted that 32-bit Office 365 saves macro documents with a VBA Project version of
B2 00
, which I didn't expect because I thought it to be associated with 2016x64 and 2019x64:https://github.com/outflanknl/EvilClippy/blob/master/evilclippy.cs#L508
Didier Stevens wrote about this phenomenon and didn't seem to reach a conclusion on why this is:
https://isc.sans.edu/diary/Office+2021%3A+VBA+Project+Version/28150
I would have simply guessed that the same p-code compiler was carried forward from 2019, but if that were true, I would have expected the version to be
AF 00
like the other recent 32-bit versions instead of the version number that has been associated with 64-bit.By way of letting you know that O365/Office 2021 is absent from the list of valid Office versions in your
switch
construct, I thought I would ask if you've encountered this too and learned anything about it?The text was updated successfully, but these errors were encountered: