0
Recently, i bought a used laptop and wanted to upgrade to Windows 10. I used an original Windows 10 home .iso from Microsoft's website and a Rufus utility to make a bootable USB.
The installation process goes smoothly at first: I choose partitions to install, and it finishes. Then it reboots. Then the Windows boot screen appears ('getting things ready' or something). And then, a blue screen with white loading circle appears with text under it 'Just a moment...' - and it keeps going like this infinitely.
I tried many things, including:
- Rebooting and trying again;
- Running system repair; after rebooting through there, it finally boots, but it requests password for 'defaultuser0'.. which is an impasse (right?)
- Creating new user in cmd - it boots defaultuser0 anyway, and i can't switch it (commands used: 'net user /add [username] [password]' and 'net localgroup administrators [username] /add')
- Trying installing other .iso images of other windows builds - but the same symptoms appear
- Trying other tools for usb creation and installing successfully with them - but that infinity loading appears anyway
I suspect that the problem is in the keyboard, though i have no idea how to fix it. It looks like the right 'shift' key is pressed all the time. And on that moment - when installation ends and it starts setting everything app - 'sticky keys' warning beeping appears, and that table appears too ('do you want to turn on sticky keys?'). And after few seconds (regardless if i press yes or no), SUDDENLY the blue infinite loading screen appears (the same i described above).
The previous owner was having problem with the shift key, and he couldn't fix it. He just could apply a weird partly-fix - he would turn on the screen keyboard and press '2' - and after that numbers can be typed on physical keyboard again (the main problem wasn't the shift, but the fact that u can't use numbers - it typed @#€_& instead. The partly-fix eliminates this problem, and keyboard becomes even usable - only right shift doesn't work)
Do you have any ideas about this? Or maybe a method to fix/disable that keyboard through BIOS or cmd (so i could use an external keyboard)?