So I have installed WSL as soon as it was available in the production ring of Windows 10. It is nice/epic etc. you should try it yourself. I used it Format a large XML file fast so that I could actually read it. That was a year ago. So it has been around now for a while.

Scott tweeted that you can pipe '|' stuff between windows/powershell and linux commands! But in the screenshot there was this "wslconfig /list" command. It listed “Legacy (Default)” for me…

Everytime a software developer says “legacy” they should wash their mouth. So I had to remove it!

Scott pointed me to this article about updating the WSL. But I did not want to update it, because I have the latest from the store. That article is also a year old by the way.

So the command you are looking for in case you have a legacy WSL as default is “lxrun /uninstall /full /y

Today (19th of April 2018) there are several options in the store:

Debian GNU/Linux https://www.microsoft.com/store/productId/9MSVKQC78PK6
Ubuntu https://www.microsoft.com/store/productId/9NBLGGH4MSV6
openSUSE Leap 42 https://www.microsoft.com/store/productId/9NJVJTS82TJX
SUSE Linux Enterprise Server 12 https://www.microsoft.com/store/productId/9P32MWBH6CNS
Kali Linux https://www.microsoft.com/store/productId/9P32MWBH6CNS

Try some and enjoy!

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn

I was trying to create new packages for a Store application and got this error. I was updating my Nest Thermostat application and adding the new Navigation View component. Which is a great new XAML component.

The docs for the navigationview xaml control are great. But during the creation of the new store package I got this dummymodulereference error… Here is my attempt to fix it:


  1. cleared all nuget caches
  2. removed the .vs hidden folder in my solution folder
  3. removed in each project folder the bin and obj folder
  4. removed the project.lock
  5. Had to open my solution file in notepad++ to see that I had a project in my solution in an other (parent) dir. So had to remove bin and obj and project.lock there too.
  6. right click on solution in the solution explorer and restore nuget packages
  7. build –> rebuild solution

But unfortunately..  I Googled with Bing and found people having similar issues: https://developercommunity.visualstudio.com/content/problem/133644/internal-compiler-error-5.html

and https://developercommunity.visualstudio.com/content/problem/137629/error-on-build-for-store.html

I even removed the symbol cache (tools –> options –> debugging –> symbols –> empty symbol cache)

Also skipped the nuget restore, because creating store packages will auto restore nuget packages.

I found out that the issue was in a global nuget package:


So I added a reference in my store app project to the same nuget but a newer version. Not 1.7.1 but 2.0.0

That did not help, so I added the microsoft.net.native.compiler package to all my referenced projects.

Also no fix. Last resort: tweet to @VisualStudio because it is already listed in the vs feedback.

Please let me know if you have a solution.

Pin on pinterest Plus on Googleplus Post on LinkedIn

My Surface Pro 3 died last October which had my bitcoin wallet on it. I forgot that I had any. I had bought them a (long) time ago for about 10 euro if I remember it correctly. But since the hardware crash of my sp3, the rate went up. Way up….


I decided to look into my backup and try to restore my wallet to see how much I had and how much it’s worth today. I had multibit classic in the beginning and upgraded to multibit HD 0.5.x back then. During the move from classic to HD I forgot my wallet words and only had my password and the backup AES wallet files.

I started my first recovery attempt on may 30th, but failed because I had no wallet words.

My second try was last week as I found this GitHub repo with a python script which can extract words from a backup file if you have the password. Sort of brute force “attack”. https://github.com/gurnec/decrypt_bitcoinj_seed

So I installed python 2.7.x alongside with 3.6 which I already had. and ran the PowerShell script.

I had a Windows 7 style backup by the way of my Win10 device and had to navigate to “C:\Users\myUsername\AppData\Roaming\MultiBitHD” and restored the full content of that folder to a new folder on my desktop. Please do not forget to check the box to have the original folders restored. Otherwise it will replace files with the same name and path references will be broken.

But somewhere in the mutlibithd is the rolling backup which you can restore once you have your password and wallet words…. so I thought.

But the amount stayed unconfirmed. So it’s useless. I have seen a lot of people with this exact same issue. Some moved away from multibitHD just because of this. The solution was not that obvious. It also did not work for everyone.

I had to downgrade to MultiBit HD 0.1.1 https://multibit.org/releases/multibit-hd/multibit-hd-0.1.1/

and renamed “C:\Users\myUsername\AppData\Roaming\MultiBitHD” to “C:\Users\myUsername\AppData\Roaming\MultiBitHD-old” and re-restored the wallet with the password, wallet words and backup file.


It is weird to have the old 0.1 version, but I am glad that it is confirmed again and in my wallet. Now I can step away to alternative wallets.

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn

Make sure you have Windows 10 with the anniversary update or newer.

You can verify this by pressing the winkey + R and type ‘winver’ and hit enter. The anniversary update has buildnr 14393. And make sure that you have the “Bash on Ubuntu on Windows” feature enabled.

Xmllint is not included by default, so you have to install it first.

sudo apt install libxml2-utils

You can read more about xmllint on http://xmlsoft.org/

in order to format a large XML file which has no line breaks you have to use xmllint like this:

xmllint --format input_xml_file.xml > pretty_output_xml_file.xml

You use the format option on the input_xml_file.xml and redirect the output (>) to a new file with the name pretty_output_xml_file.xml

This is a lot faster than opening the file in notepad++ and use the xml plugin to format it.

Hope it helped. Good luck!


Pin on pinterest Plus on Googleplus Post on LinkedIn

Here are the 9 steps to enable the linux subsystem in the latest Windows 10 version:

  1. Windows key + I (to go to settings)
  2. Update Windows
  3. Select developer menu on left hand side
  4. Make sure that the developer mode is enabled
  5. Go back to the main page of settings
  6. On the right hand side click “programs and features”
  7. Click on install additional features on the left hand side
  8. Check the box for the linux subsystem
  9. Double click on c:/windows/system32/bash.exe to install it



I had to blog this, because the GUI option mentioned on msdn did not work on my locale (nl_nl)



Read more about it on MSDN https://msdn.microsoft.com/en-us/commandline/wsl/about

Good luck!

Pin on pinterest Plus on Googleplus Post on LinkedIn