I have already talked about why I am no longer using Windows 10, and the Electronic Frontier Foundation has some great reasons why I will continue to avoid using it until it is appropriately fixed.
I was working on a new laptop for a client (preapring a basic setup and installing some software solutions for his business) that came pre-installed with Windows 10 and no support media. After a nominal wait for the OS to perform its “first run” checks and setup, I was presented with the Windows 10 login screen, but the only user account available was this “defaultuser0”, which I did not have the password to. Normally, I would refer to the manual (or quick start guide in a pinch), but the refurbished Acer from Newegg came with only a single slip of paper explaining the warranty. My years of experience with Windows taught me that the first step in troubleshooting is to reboot (possibly into Safe Mode) which you can technically only do from inside Windows, so I did the next best thing: a hard power-off reset.
Yes, I know you’re never supposed to do that. Sometimes you have no alternative but to use a little brute force.
Upon the reset, Windows returned to the initial setup screens, asking me for language, keyboard layout, and prompting me to leak as much data as possible back to Microsoft (to which I always opt out). So far, so good; however, after an unusually long “Just a moment…” screen, the monitor dropped to a blank screen with only a cursor. All the information that I was able to locate pointed to a driver problem and that the screen would initialize after a prolonged wait. That was a sucker test. I waited an entire day before giving up the ghost on that idea.
After much gnashing of teeth, I was able to assemble a solution from several partial solutions scattered through the Windows 10 fora, but lucky you, I’m going to share the fruits of my labor!
First thing to do in this situation is perform the hard reset. Hold the power button until the computer turns off. Wait a few moments for the hard drive(s) to stop spinning before powering the computer on again.
Once Windows gets as far as the Regional Settings dialog (the screen asking for language, time zone, and keyboard layout), press CTRL+SHIFT+F3 to reboot the computer into audit mode. Once you’re finally “properly” into Windows, ignore the System Preparation Tool window, open the Start Menu, then click “Power”. Hold down the left-hand SHIFT key, click “Restart” and keep the SHIFT key held until the reboot options screen appears.
Click “Troubleshoot”, then “Reset This PC”, and finally “Remove Everything”. You’ll drop to a black screen with the word “Preparing” in the large, friendly letters characteristic of Windows 10. Eventually, you will return to a blue screen asking if you want to clean the drives as well. Click “Just remove my files” and then the “Reset” button on the next page. The screen will go black again and display the Windows 10 progress indicator while it chugs through the reset process.
Grab yourself a beer and watch some cartoons because it will take a while to finish, but when it completes Windows should be ready to play nicely during setup, and not throw you another defaultuser0 error.Also on:
Okay, Mr. Nadella, you have my attention….
You’ll soon be able to run Ubuntu on Windows 10.
Ever the optimist, I jumped feet-first into Windows 10 on the VCR, because there isn’t much documentation on the sorts of things I’m trying to do with Windows and the project. For the past couple of weeks, I’ve been blazing a trail through the digital wilderness trying to get peripherals and software working perfectly under the new OS, and I hate to say that I’ve run across some glaring dead-ends.
The first to go was the real support for my remote control. Because it uses the MCE protocol, which is no longer supported by Windows 10 (since they dispensed with MCE in a vaguely boneheaded move to sell more XBones? [Pun intended]). WinLIRC, which was already a finicky primadonna under 7 has simply refused to work more than once under Windows 10. The Xbox 360 remote still works (sorta), but I prefer to have the different protocols so I’m not transmitting odd signals to one machine or the other. I’ve been having to use a keyboard and mouse combo primarily for simple navigation, which is getting old, so I decided to give the gamepad a go. Which leads to dealbreaker number 2.
Either Logitech is not supporting its devices properly or Microsoft has decided to abandon support for generic X-Input devices. Probably both. Logitech has taken the official position that gamepads should use Direct-Input and map controls through their proprietary software which immediately does not work because I lose the programmable functionality of the “Guide” button which I will make extensive use of in future upgrades to the system.
It stands to be said that the only reason I am using Windows in the first place is for proper game support. Instead of a hacked-up solution involving WINE under Ubuntu, I would rather have the operating environment with minimal “intrusion”. Granted, for media and hardware support, I would rather be running under Ubuntu anyway, but I’ve got to sacrifice one to get the other.Also on:
It used to be fairly easy to find things in Windows 7, but after 8, Microsoft decided to start hiding system settings under oddly generic menu headings. This has become a tradition now in Windows 10, which makes it somewhat difficult to find the correct user settings to automatically log into Windows.
The easiest way, of course, is to ask Cortana. Type “netplwiz” into the search bar. This will bring up the list of accounts on the computer. Highlight your account (or, if you’re like me and the only user, the Administrator account) and uncheck the box next to “Users must enter a user name and password to use this computer”.
Upon restart, you should no longer be prompted for a password with that beautiful Pacific beach scene. Oh, well.Also on:
“Fast Boot” is some sort of new “hybrid shutdown” feature that Redmond came out with in Windows 8, but since no one used that stub of crap, everyone (myself included) thought it was a new feature in Windows 10. Either way, it’s a great feature that really speeds up the boot time through some sort of Windows OS magic! In my copy, it was turned on by default, but just in case yours isn’t (or just to ensure that it is), it’s a fairly simple task to enable fast boot in Windows 10.
Ask Cortana for Power Options (in other words, type “power options” into the search bar; it should be the first result). You can always navigate Control Panel -> All Control Panel Options -> Power Options.
On the left sidebar, click “Choose what the power buttons do”.
In the “Define power buttons…” dialog, click the “Change settings that are currently unavailable” option.
Under “Shutdown settings”, make sure the fast startup option is checked.
Save settings, close, and you’re all set!
Source: Redmond PieAlso on: