After you fresh install Windows 10 on your computer, it allows you to set up a PIN just before you can start using it. However, a number of users reported that the Windows 10 installation gets stuck on the “Set up a Pin” phase. If you are one of the users who experience the same thing, then read on as this post will walk you through fixing the problem.
As users start to use their newly installed Windows 10 computer, they reported that the screen is still stuck even after they enter the correct PIN twice and there is no way for them to go forward or backward. Note that this is a part of the account setup and that your computer must stay connected to your internet connection before you finalize everything. And even though the PIN works when the computer is offline, the account setup still needs an internet connection, at least for a fresh installation.
The solution for this kind of issue is quite easy and there won’t be any problem even if your computer shuts down or restarts since the installation is already complete and all that’s left is the account setup. To fix this problem, follow the steps given below.
Step 1: The first thing you have to do is to turn off your internet connection or disable all connectivity from your computer.
Note: If you are using either an Ethernet cable or a Wi-Fi switch to connect to the internet, you have to disable or remove them. But if you don’t have any options, just completely turn off your internet connection.
Step 2: The next thing you have to do is to force your computer to shut down and then restart your computer. The setup process will eventually pick up exactly where it left off. The only difference is that there is no connection to the internet and your screen will no longer be stuck on the PIN setup screen so you now have the option to skip it and wait until you’re logged in for the first time.
Step 3: Once you’re done, you can then you can choose to Setup Pin later on and turn your internet connection back on or connect your computer with an internet connection.
The author of the famous software library mode-ipc that gets over a million downloads per week found that it has some questionable code inside. The code itself behaves like this: if it finds out that your location is within Russia or Belarus it will try to replace the contents of all files on the computer with a heart emoji.
One important thing is that we here are not supporting the current Ukrainian situation and are against any type of violence or war but we also do not support this kind of behavior as well. If we look at this only from a technical perspective, we would then classify the mode-ipc library as malware and a harmful piece of code no matter the motivation behind it.
So this so-called protestware is well basically malware, but not always, it will protest when certain conditions are met. The issue with this is that companies and users should not be placed under harm if they do not share the personal view of the code author. Imagine if, for example, I would publish code to delete all pictures from your computer if my code found out that you do not like metal music. I guess you not liking metal music and war in Ukraine are two very different things but the source is the same, unreliable code that invades your privacy in order to serve one purpose, punishment for disagreeing with my personal views and that should not be allowed.
Not all protestware are equal, some will not harm your computer on purpose, they will just annoy you with some messages like viruses did in their infancy stages, others might place some developer sanctions but no matter the outcome basic principle is the same, it does something without user consent and without informing the user that something like that might happen.
On the internet, many blog posts and discussions were open about this issue and its morality. Discussion is still active with different takes on the situation and how to prevent it. Our take on this matter is that professional developers should have standards and not submit to doing harm for the sake of personal views and feelings.
In the long run, this kind of behavior and practice can only harm developers involved in this kind of entanglement. Infected libraries will in time stop being used since people would not trust them and authors will have a stain on their name as impulsive or not trustworthy.