My Windows laptop doesn’t seem to want to run Windows anymore

A week ago, I was sure I could cure the squirrelly behavior of the laptop I bought less than six months ago the hard way–by wiping the hard drive and reinstalling Windows from scratch. And for at least two days, that worked.

But then the laptop failed to wake from sleep, and when I force-rebooted it, the machine got stuck in the same “Preparing Automatic Repair” state that left this HP Spectre x360 unusable for a few days last month.

And this time, the laptop was back to refusing to recognize the USB recovery drive I’d created on it–even while it did boot up my ancient ThinkPad.

A chat session with HP’s tech support didn’t unearth any fixes for the problem, so the rep said he’d send me a second USB recovery drive. To HP’s credit, that drive arrived the next day.

But while this “Recovery Media” can erase the hard drive and reload all the necessary installation files on its recovery partition, the computer can’t then load Windows off that partition. At some point into the installation process, it gets stuck at a blank screen that features only Windows’ spinning circle of dots.

The Kafkaesque angle to all this: Installing Ubuntu Linux off a flash drive was no problem at all. Alas, this distribution of the open-source operating system doesn’t seem to recognize my laptop’s touchscreen, fingerprint sensor or Windows Hello facial-recognition cameras, so it’s not a long-term solution.

My next attempt will be to create a Windows recovery drive from the disc image you can download off Microsoft’s site. But if that doesn’t work either, this laptop’s next business trip will involve it going back to HP in a box.

Advertisements

A non-automatic repair of a mysteriously-hapless HP laptop

I went a few days without using my laptop, but that wasn’t actually part of the plan for our kid’s spring break. Having this HP Spectre x360 inoperative did, however, teach me valuable lessons about computing preparedness, which I will now share so that you may benefit from my experience.

(And so that Mac fans can dunk on me for my latest laptop purchase. I know what I’ve got coming…)

As far as I can tell, things started going sideways with the laptop last Wednesday. That’s when it failed to wake from sleep, I force-rebooted it, and it started into a screen saying Windows was “Preparing Automatic Repair.” There it stayed through multiple reboots until I set it aside for a few hours and finally saw it had returned me to the Windows “Recovery Environment.” From there, I could order up a System Restore that brought the PC back to health.

HP laptop stuck on repair

Except the same “Automatic Repair” message reappeared two days later and kept coming back. By then, I had learned that I was not alone in seeing this alleged repair stall a startup.

I gave up and did a “reset” of Windows Sunday. That clean reload of the operating system left my files intact but required reinstalling every app, re-typing every saved Web login, and even redoing things as basic as apps pinned to the taskbar and the Start menu–it reminded me too much of factory-resetting an Android phone three years ago. Alas, that evening, the laptop again failed to wake from sleep, then after another forced restart got stuck on the now-dreaded “Preparing Automatic Repair” screen.

I had thought to create a Windows recovery USB flash drive while my laptop was working Sunday. But the laptop ignored it every time I tried to boot from it.

After two days of fruitless troubleshooting–during which I did work in an incognito window on my mother-in-law’s MacBook Air, as if it were an overpriced Chromebook–I thought to try booting the HP off a USB flash drive loaded with Ubuntu Linux. That got the machine back online, so at least I knew the laptop’s hardware remained sound.

A Twitter conversation with my friend Ed Bott reminded me to try the Windows recovery USB drive on another computer, where it did boot–and on my next try using that in the HP, it finally started up the laptop. (This is not the first time I’ve needed to borrow somebody else’s device to breathe life into an uncooperative bit of circuitry.) Command-line tinkering found no issues with the HP’s solid-state drive or the Windows installation, so I did yet another system restore and finally had my computer back.

I’m typing on the same machine seven hours later, so hopefully things took. But if not, I now have two flash drives that I know can boot the machine. If you have a Windows PC, please learn from my ordeal and take a few minutes today to create a recovery flash drive for your machine.

And if that PC insists over hours that it’s preparing an “Automatic” repair, remember that when Windows keeps using that word, it may not mean what Windows thinks it means.

My no-longer-secret Bitcoin shame

Bitcoin has infested tech news lately–the cryptocurrency’s unlikely rise in value, its subsequent and unsurprising fall in value, what complete tools Bitcoin zealots can be in front of a reporter, and so on and on. I’ve watched all of this as an unwitting spectator.

Yes, I’m one of those doofuses who forgot a password to a Bitcoin wallet. At least I have a half-decent excuse: CES.

I didn’t go to the gadget show in 2014 planning on investing in Bitcoin, but one of the first events I attended featured a diverse contingent of BTC startups, one of which had a dollars-to-Bitcoin ATM. How could I not gamble a few bucks to earn an anecdote to throw into a Bitcoin explainer?

I put a $5 bill into this thing and followed an exhibitor’s advice to install the Mycelium wallet app on my phone, scan a QR code off the ATM’s screen, and set a 15-character passcode to protect my stash of .00513 BTC.

Guess what I forgot to do as I headed to my next CES appointment?

I then mostly ignored the app, except for the occasional check to see how my investment had decayed. That habit faded, and when I tried resetting my phone the next fall to fix some touchscreen bugginess, I didn’t even think about the risk of losing access to my tiny Bitcoin hoard.

By which I mean, I didn’t even think to open Mycelium until several months after that unsuccessful phone-troubleshooting exercise. Then I realized that I could no longer remember the 15 characters I’d typed on my phone’s screen two years earlier, without which I could not restore the backup I had made right after my ATM transaction.

That’s where things have remained, even as Bitcoin’s value has soared and then plummeted. It’s annoying, but at least I have two things going for me: The app won’t lock me out as I keep guessing the passcode incorrectly, and at the current exchange rate I’m only out $57 or so. I’ve done much worse gambling in Vegas.

Sharing stories from Apple News considered harmful

Last Tuesday, Google delivered some news that open-Web advocates have long awaited: Stories posted in the speedy, Google-developed Accelerated Mobile Pages format and served up via its even-faster caching service won’t zap onto the screens of mobile devices at google.com addresses, not the domain name of their publisher.

The avoidable but common facet of the AMP experience has bothered me since my early encounters with Google’s attempt to make the mobile Web less janky–it led the explainer I wrote for Yahoo two years ago. Google is now moving to fix the problem it helped create, which is welcome news in any publishing format.

(Specifically, Google will adopt a new page-packaging standard to preserve site domain names. In last Tuesday’s post, AMP project tech lead Malte Ubl says we should start seeing the results on our phones in the second half of this year.)

This, however, leaves another address-eating annoyance on the mobile Web: Apple News. This iOS app is a pleasant way to browse and read stories; like the open-source AMP, this proprietary format cuts out the cruft that can clog mobile reading.

But when you tap its “Share” button, Apple News serves up an apple.news address. And unlike even Googled-up AMP addresses, this one offers no hint after the domain name of where you’ll go.

The text Apple News pre-populates in a tweet or Facebook update–the story headline, an em-dash, and then the publication name–does. But on Twitter and Facebook, many people decide to replace that text with their own words, leaving users to guess what’s behind that apple.news address.

Apple appears to be doing this to ensure that other iOS users can read the story you shared in Apple News as well–its developer documentation even lists a story’s canonical address as a “not required” bit of metadata. But in the context of a button that can share a story on the public Web, that’s an absurd inversion of priorities.

Apple could fix this by coding Apple News to share a story’s original address when available, perhaps with an identifier to tell iOS devices to open it in Apple News. But knowing this company, I wouldn’t expect that any sooner than the arrival of a reborn Mac mini at my neighborhood’s Apple Store.

Instead, you’ll have to solve this problem yourself. If you’re sharing a story from Apple News, keep some reference to the publisher in your description. If that would cramp your social-media style, please take a moment to tap the share sheet’s “Open in Safari” button–then share the story from that browser, from whence it will have its real address.

CES 2018 travel-tech report: Ethernet lives!

I survived another CES without having my laptop or phone come close to running out of power during the workday, which is worth a little celebration but may also indicate that I did CES wrong.

One reason for this efficient electrical usage is that I showed up in Vegas for a new laptop for the first time since 2013. The HP Spectre x360 laptop that replaced my MacBook Air couldn’t get through an entire day without a recharge, but plugging it in during lunch and any subsequent writing time freed me from having to think about its battery for the rest of the day.

The Google Pixel phone I bought last summer was thirstier, mainly because I could never really put that down even after dark. But I still never needed to top off the phone with the external charger I bought.

Having both the phone and laptop charge via USB-C delivered an added bonus: Whenever I was sitting near an electrical outlet, I could plug either device into the laptop’s charger.

CES telecom, however, got no such upgrade. The press-room WiFi worked at the Mandalay Bay conference center but often did not in the media center I used at the Las Vegas Convention Center. And having to enter a new password every day–what looked like a misguided episode of IT security theater–did not enhance the experience.

Fortunately, the cheap USB-to-Ethernet adapter that my MacBook had inexplicably stopped recognizing a few years back worked without fuss on the HP so I often reverted to using wired connections. The irony of me offering an “it just works!” testimony to a Windows PC is duly noted.

T-Mobile’s LTE, meanwhile, crumpled inside the Sands and often struggled to serve up bandwidth at the LVCC. More than once, this meant I had to trust my luck in CES traffic when Google Maps coudn’t produce any road-congestion data.

I packed two devices I’ve carried for years to CES but only used one. The Belkin travel power strip I’ve brought since 2012 avoided some unpleasantness in a packed press room Monday but wasn’t necessary after then. The Canon point-and-shoot camera I’ve had since 2014, however, never left my bag. The camera in my Pixel is that good for close-up shots, and I didn’t come across any subjects that would have required the Canon’s superior zoom lens.

I also didn’t come across a worthy, pocket-sized successor to that “real” camera at any CES booths. But with some 2.75 million square feet of exhibits at this year’s show, I could have easily missed that and many other solutions to my travel-tech issues.

Recommended Precision Touchpad settings

I’ve yet to ease into a new computer without having to fuss with some of the default settings, and the HP Spectre x360 laptop sitting on this desk has fit right into the pattern.

Most of the tweaking has involved its touchpad, because I’ve always found the defaults in Windows to be too jumpy. (I’ve said the same about some Mac touchpad defaults.) But after a few days of clicking around the stock Synaptics software, I realized I should first dump that for drivers supporting Microsoft’s more elegant Precision Touchpad software.

The directions I found on Reddit (embedded here after the jump) worked, and then I could easily shut off the touch behaviors I couldn’t stand.

  • “Touchpad sensitivity”: I changed this from the default “Medium” to “Low” because, again, jumpy touchpads bother me. I may try turning it back off to see if disabling the following two options made the standard sensitivity acceptable.
  • “Tap with a single finger to single-click”: This is the one setting I change on every laptop. If I want to click, I’m more than happy to press down so the touchpad makes an audible click; having it treat a stray touch as a click leaves me randomly dumping the cursor into documents and windows and feeling generally stabby as a result.
  • “Press the lower right corner of the touchpad to right-click”: I disabled this because it’s easier for me to remember to tap with two fingers to right-click than to keep track of which side of this invisible line I’m about to tap.

I hope this advice–which should also work on any other laptop running Microsoft’s Precision Touchpad software–makes for a more pleasant laptop computing experience. If you have other suggested settings changes, please share them in the comments.

Continue reading

Early impressions from a late Pixel adopter

Not that many people have bought either of Google’s two Pixel phones–as little as one million as of June, per Ars Technica’s estimate–and I bought my Pixel later than most.

And Wednesday, Google will introduce the replacements for the Pixel and Pixel XL, so this will be one of my less relevant reviews ever. But I still think it worthwhile to write down my three-months-in impressions… just in case I hate the phone later on.

But so far, I don’t. For something that I thought would be an interim advance over my now-dead Nexus 5X, the Pixel has impressed me.

The most pleasant surprise has been battery life that frees me from having to look for a charger on normal days–reading, I’m not at CES or some other phone-battery-destroying event, but I still leave the house and do my usual poor job of avoiding social media. I realize that sounds like thin gruel, but it also represents progress.

The camera has been an unexpected delight, easily the best I’ve used on a phone and more than good enough for me to leave my “real” Canon in my bag at the IFA trade show two months ago. Seriously low-light indoor exposures can still flummox it, but for the vast majority of my shots it delivers great results. The HDR function does some particularly amazing work with fireworks and illuminated structures at night. But judge for yourself: Have a look at my Flickr and Instagram feeds.

My major gripe with this phone is a weird one: It seems too easy to unlock. As in, the positioning of its fingerprint sensor seems to catch my finger more than the 5X’s sensor did when I slip it into a pocket.

So far, I have only pocket-texted one person–“App eye, meàl,” the message began before sliding into complete incoherence–but that was embarrassing enough to get me to try to grab the Pixel by its sides when pocketing it. And to change its “Automatically lock” screen setting from five seconds post-sleep to immediately.

If the rumors are true, the Pixel 2 and Pixel 2 XL Google will introduce Wednesday won’t feature expandable storage but will drop the headphone jack. If so, that will make me feel pretty good about taking Google on its offer of a full refund on my bootlooped 5X and applying that to a Pixel.
But it will also leave me profoundly uneasy over what my next Android phone will look like. I don’t want an uncompromised Android configuration to be a deeply compromised choice of outputs.