If you're interested in inventory and documentation, take a look at the  XIA Configuration review recently posted on the 4sysops website, an online community for SysAdmins and DevOps. The review is written by Timothy Warner who is a Microsoft Cloud and Datacenter Management Most Valuable Professional (MVP).

I created a System Data Source with an Oracle driver and gave it the name "1Data Source Name" I then changed the Data Source Name to "Aéü1 "#$a%&'+-./:<>^_`|~£©™" Upon pressing OK, I discover that my System Data Source has been duplicated and I now have two entries, one with the original data source name and one with the new data source name! I seem to be finding a few bugs in Windows lately!

I found another bug whilst testing Windows files on my virtual test environment. I made a folder on my host machine which contains a couple of test files as follows: C:\aAéü1 !#$%&'()-.@^_`{}~£©™\aAéü1 !#$%&'()+,-.;=@[]^_`{}~£©™.txt C:\aAéü1 !#$%&'()-.@^_`{}~£©™\aAéü1 !#$%&'()+,-.;=@^_`{}~£©™.txt I then dragged and dropped the folder onto my virtual machine and was shocked to see that a square bracket had been inserted into both file names! C:\aAéü1 !#$%&'()-.@^_`{}~£©™\aAéü1 !#$ ] %&'()+,-.;=@[]^_`{}~£©™.txt C:\aAéü1 !#$%&'()-.@^_`{}~£©™\aAéü1 !#$ ] %&'()+,-.;=@^_`{}~£©™.txt These particular file names are obscure but I do wonder if this could happen in circumstances with more conventional file names that happen to include characters that trigger this bug!

I've recently been testing files with different names in Windows using a long set of special characters: aAéü1 !#$%&'()+,-.;=@[]^_`{}~£©™ Part of this testing involved copying these files and I noticed that the round brackets are automatically removed by Windows when doing so! aAéü1 !#$%&'+,-.;=@[]^_`{}~£©™ - Copy This only seems to happen if the curved brackets do not contain any text.  If you put some characters between the brackets, they remain when the file is copied.

This post describes how to fix error 0x80041013 'Provider load failure' which can occur when using the Windows Management Instrumentation Tester (wbemtest) to run a WMI query: Screenshot of error 0x80041013 Cause This error can occur when wbemtest does not have sufficient privileges to load the required provider. Resolution To fix this error, run wbemtest as an administrator: Your query should now execute successfully. Screenshot of a query in wbemtest Video YouTube link:  0x80041013