In the documentation https://github.com/decalage2/oletools/wiki/olevba, it says "MS Office files encrypted with a password are also supported, because VBA macro code is never encrypted, only the content of the document". This makes me think, for an encrypted office file, olevba can extract the macro with or without a password provided. However, this is not the case. olevba seems only extracts the

Justification
As a convenience to aid support issues, the "friendly" name of the Windows installation should be looked up from the raw version number.

Description
Currently, the RD logs OS version shows as a raw number, e.g.
Operating System: Microsoft Windows NT 6.2.9200.0 x64

Whilst this is technically correct, it's not particular

Parsing error on this sample: https://app.any.run/tasks/2be2b38f-4de2-4b48-8ae5-67bda9eecbaf

-------------------------------------------------------------------------------
PARSING VBA CODE:
INFO     parsed Sub z55e6df583 ([ByVal s2b7d47c629 as String]): 14 statement(s)
INFO     parsed Sub Document_Open (): 5 statement(s)
INFO     parsed Function tfaca84885f ([ByVal zd77f34558c as Varian

The RangeDeserialize and RangeDeserializeBuilder functionality is great but it's not immediately clear that these functions are closely integrated with serde. All the examples show the values being deserialized into a tuple but I think it would be good to have at least one example somewhere showing how it can be deserialized into a struct in combination with serde.

I wasn't sure how to get the server working... here's where I'm at:

Struggled with PowerShell (first time using PS_ISE):
When I opened a file in PS-ISE I didn't notice that I still needed to navigate to the working directory in order to load the other files.

Server started, what should be expected?
When I started the server, as expe

@mattpalermo I'm not sure if this is taken care of anywhere already but

Here's my experience, have the source code somewhere on your machine, go to build the add-in, so for me I know how to build the Excel .xlsm from the source then add the modules all groovy, then I compile...

I know that there are some refs need adding and I could just go through and hit compile and add in the refer

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

Specifications

• Version:
• Platform:
• Subsystem: