Author of Beej's Guides.
1770 stories
·
2 followers

Courts Close the Loophole Letting the Feds Search Your Phone at the Border

1 Share
Comments
Read the whole story
beejjorgensen
2 hours ago
reply
Bend, OR
Share this story
Delete

Giant phallus-shaped iceberg floating in Conception Bay

1 Share
Comments
Read the whole story
beejjorgensen
1 day ago
reply
Bend, OR
Share this story
Delete

User returns after 100k-hours ban to continue conversation that got them banned

1 Comment and 2 Shares
Comments
Read the whole story
fxer
2 days ago
reply
Of course it’s a goon
Bend, Oregon
dreadhead
2 days ago
"No, I am not revealing my username."
beejjorgensen
4 days ago
reply
Bend, OR
Share this story
Delete

I mapped almost every USA traffic death in the 21st century

1 Share
Comments
Read the whole story
beejjorgensen
6 days ago
reply
Bend, OR
Share this story
Delete

The Commodore 900: A Look at a Rare Prototype

1 Share
Comments
Read the whole story
beejjorgensen
7 days ago
reply
Bend, OR
Share this story
Delete

CrowdStrike fixes start at “reboot up to 15 times” and get more complex from there

1 Share
CrowdStrike fixes start at “reboot up to 15 times” and get more complex from there

Enlarge (credit: hdaniel)

Airlines, payment processors, 911 call centers, TV networks, and other businesses have been scrambling this morning after a buggy update to CrowdStrike's Falcon security software caused Windows-based systems to crash with a dreaded blue screen of death (BSOD) error message.

We're updating our story about the outage with new details as we have them. Microsoft and CrowdStrike both say that "the affected update has been pulled," so what's most important for IT admins in the short term is getting their systems back up and running again. According to guidance from Microsoft, fixes range from annoying but easy to incredibly time-consuming and complex, depending on the number of systems you have to fix and the way your systems are configured.

Microsoft's Azure status page outlines several fixes. The first and easiest is simply to try to reboot affected machines over and over, which gives affected machines multiple chances to try to grab CrowdStrike's non-broken update before the bad driver can cause the BSOD. Microsoft says that some of its customers have had to reboot their systems as many as 15 times to pull down the update.

Read 8 remaining paragraphs | Comments

Read the whole story
beejjorgensen
7 days ago
reply
Bend, OR
Share this story
Delete
Next Page of Stories