It is possible that this behavior has already been corrected. I personally have not experienced it. Once it finishes sweeping the network and identifies the elements, it should allow configuration. Does it happen only on that particular pc?

I would try the latest version.