FYI: Importing wifi credentials via MrC Converter Suite [Solved]

SKSSF

Thanks for the details. This is all leading me to believe there is something wrong with your CSV file, because too many things are not working. I'll enumerate:

1. You don't need "--imptypes wireless". The csv converter automatically detects the type based on the column labels.
2. The values in the non-labels rows cannot affect the type of record detected. Only the labels matter for this converter.
3. Given that your first test above failed, I'm certain this is an issue with the CSV export. Any of the labels besides Title and Notes would have caused detection as type = 'wireless' .
4. The labels really are case-insensitive.
5. You mentioned "wifi credential" above. The csv converter has no such category, so it must have been something else.
6. You will only get columns placed in an Original Fields section when a label doesn't match a known label. While your labels look correct in the screenshots above, only the CSV data itself can verify this.

The image below shows a dump of a simple 3 column CSV file, and debug output running the converter against it. The data is detected as 'wireless'. It has only one column other than Title or Notes, and that label is case-varying.

I don't have Excel installed in my VM's, nor am I up to date on all of the CSV export options it provides. It is important that the CSV is UTF-8 encoded, and follows correct CSV rules. There's some leniency with quoting. My guess is that the file encoding is incorrect, or the labels are not string matching the required labels names (case ingnored).

If you could create for me a non-working CSV file with one label row, and one dummy data row, I can diagnose the issue and we can resolve this. I'll need the raw file, not copy/pasted text. You could email it to me - my email is at the top of all the script files.

While we're chatting, can I suggest a feature--the ability to convert the output from
netsh wlan export profile key=clear folder=c:\path
directly into a 1pux file...or converter for the output from this PowerShell script?

This wouldn't be something I could do, or would want to maintain. All my Windows work is done in VMs, and there's no WiFi there (the network comes from the host, either shared or bridged). So no wlansvc running, hence netsh wlan will fail. I wouldn't begin to know the output variations in that plain text dump, and lacking the ability to generate actual test data, it would be endless guess work. Some enterprising person might adapt that PowerShell script to produce the appropriate CSV file for the csv converter's consumption.