I think the signs of a departure from Twitter are all there. Certainly on a cellphone there’s little point to it any more. As of last week, this began happening.
If you donât seesee me on Twitter as often, itâs becausebecause itâsitâs no longer compatible withwith the Swype keyboardkeyboard on my phonephone. I canâtcanât be botheredbothered correcting faults createdcrcreated by technologytechnology and not me. Other sites are fine.
That last sentence refers only to the fact that Twitter is the only website on the planet where the keyboard is incompatible. (Thanks to Andrew McPherson for troubleshooting this with me.) Other sites are buggy, too: earlier today I couldn’t delete something from Instagram (being owned by Facebook means all the usual Facebook databasing problems are creeping in), and one video required four upload attempts before it would be visible to others:
I couldn’t reply on the Facebook website to a direct message (clicking in the usual typing field does nothing, and typing does nothing) except in image form, so I sent my friend this:
Earlier this year, many friends began experiencing trouble with their Facebook comments: the cursor would jump back to the beginning of text fields, pushing the first few characters they typed to the end. Others are complaining of bugs more and more oftenâreminds me of where I was four or five years ago. And we all now know about Facebook bots, four years after I warned of an ‘epidemic’.
It’s as I always expected: those of us who use these sites more heavily encounter the bugs sooner. Vox was the same: I left a year before Six Apart closed it down, and the bugs I encountered could never be fixed. I’m actually going through a similar battle with Amazon presently, blog post to come.
Now, since Mastodon and others work perfectly fine, and there’s no end of trouble to Big Tech, it’s inevitable that we jump ship, isn’t it?
Everybody wants PS2. Still from The Professionals episode ‘Servant of Two Masters’.
I read this article in The Guardian, thinking: surely, after Microsoft rolled out some terrible updates, it wouldnât be so stupid as to do one that bricks customersâ computers again? Especially after the bug was reported a month ago.
The April update worked reasonably well, though I lost my wallpaper. But everything else was there, and I was using Vivaldi, which is a Chromium-based browser.
Then I rebooted.
That was it: my computer was bricked. The first boot, a very tiny rotating circle eventually appeared, but I couldnât do anything except move the circle with my mouse. Subsequent reboots just resulted in a black screenâsomething, I must say, I had already encountered with an earlier Windows update that saw my having to take the PC back to the shop.
I rebooted the computer three times to force it into recovery mode, but then there was another problem: neither mouse nor keyboard worked. It was as though USB was dead.
Out of sheer luck I had a PS/2 keyboard that was unused, and after more forced reboots, I was able to use the old keyboard to look at various recovery options. Remember: no input device on USB works, and this was a bug that had surfaced with the last update in February.
Forget system restore: the April update is a fresh OS, so there are no restore points.
I had no choice but to roll back to the previous version I had installed.
And here I am, back again, an hour wasted. It would probably be longer if I didnât have an SSD.
Microsoft, get your QC sorted, because this current model youâve employed over the last few years simply does not work. I have spent more hours on these updates than with any OS you have ever rolled out, and that includes XP Service Pack 3 on a comparatively ancient system.
And if you get stuck like I do, and like all those in The Guardianâs article did, I hope you still have a way of plugging in a PS/2 device and have an old-school keyboard lying around.
Since Facebook bought Instagram, itâs been getting buggier, of course.
Iâve complained about Instagram uploading a series of posts in a totally different order to what I had (which, on ANZAC Day, made it difficult for anyone to follow the story I was trying to tell on my account when the order is 2, 1, 5, 4, 3, 6, 7).
Video (2) was an interesting one, because Instagram allowed me to post something that was 2 minutes, 6 seconds long, which it had never done before (or since).
I thought it odd at the time but given that it was twice as long as normal, I didnât complain. It allowed me to show more of the Air Force band performing ‘Au e ihuâ (Soldierâs Hymn).
I did complain about one particular video featuring our national anthem which Instagram would say was loading, then on checking again, it would vanish. I made three attempts over a two-hour period before it âstuckâ (video no. 3 in the sequence above). I had to wonder if Instagram was picking up the music and flagging it as a copyright violation: after all, YouTube flags static as copyright violations (hat tip to Retrorechercher).
Above: Instagram says these two are loading, but the one featuring our national anthem (the top one) kept vanishing. It never made it on to my account without three attempts.
This morning, on checking the stats, I noticed that no one had viewed the longer video, and, after asking some friends on Twitter, learned that Instagram blocked anyone from seeing it. Itâs like shadow-banning on Twitter: you can see your own stuff, but no one else can. Try it for yourselfâhere’s the link Instagram claims it’s at.
Look at the eighth post down. On my account (top), I can see it. When logged in as someone else (above), I can’t. Instagram’s version of shadow-banning?
I can still play it straight from Instagram on the web and on my phone.
You can give the MP4 a shot here (and note the URL, which is an Instagram one, and the duration). The thumbnail is here.
However, I canât embed the video the normal way, and any link that it lets me share results in a 404. It all feels very familiar, because this is the sort of bug that Facebook used to cook up, e.g. on days when you couldnât post, like, comment or share, or tag yourself in a photograph.
I might save the two-minute-long video separately in case thereâs a way you can tell that it was edited inside Instagram.
To sum up: Instagram will not load content in the same order you do (we already know this); it will permit much longer videos that exceed one minute, but if they let it through, no one will ever see it except you. We also know that Facebook will pump through any advertising on to Instagram, even in categories you have expressly asked not to be shown.
There you have it, Instagram in 2018.
PS., April 25, 1.19 a.m. GMT: I’ve just tried a 2 minute 50 second video, and it appears it is visible. For how long, I don’t know. Check it out here, or, if the embed’s visible below, have a look.
P.PS., 1.59 a.m. GMT:Looks like four minutes is fine, too. While the first one is still invisible, it does appear Instagram has lifted the one-minute limit, and that’s not something I can find documented anywhere. Still, I’m grateful, because it makes far more sense to show two- to four-minute vids.
P.P.PS., 8.54 a.m. GMT: Just tried one at seven minutes, and it’s hidden. Seems Instagram is very inconsistent on what it shows and what it doesn’t. Link is here (it won’t work) and the MP4 is here.
As many of you know, between around December 8 and February 2âdates during which I had Microsoft Windows 10âs fall Creators update without the January 31 cumulative patchâmy computer suffered roughly three to six BSODs per day. Going on to Bleeping Computer was helpful, but Microsoftâs wisdom tended to be hackneyed and predictable.
While I was lucky at Microsoft Answers and got a tech who wasnât rehashing remarks from other threads, eventually he gave up and suggested I download the old spring Creators update, if that was the last version that was OK.
I never had the time, and on February 2, I got the cumulative patch and everything has been fine since.
It means, of course, that Microsoft had released a lemon at the end of 2017 and needed a big patch to deal with the problems it had caused. No word to their people on the forum though, who were usually left scratching their heads and concluding that the only option was a clean installation.
I had bet one of the techs, however, that there was nothing wrong with my set-up, and everything to do with the OS. We know Windows is no longer robust because of the QC processes Microsoft uses, with each team checking its own code. Thatâs like proofreading your own work. You donât always spot the errors.
I said I could walk into any computer store and find that the display models were crashing as well.
Last weekend, I did just that.
Here are the Reliability Monitors of two Dell laptops running factory settings picked at random at JB Hi-fi in Lower Hutt.
Above: The Reliability Monitors of two display Dell laptops at JB Hi-fi in Lower Hutt, picked at random.
Above: My Reliability Monitor doesn’t look too bad by comparisonâand suggests that it’s Microsoft, not my set-up, that was responsible for the multiple BSODs.
The Monitors look rather like my own, not scoring above 2 out of 10.
They are crashing on combase.dll for the most part, whereas mineâs crashing on ntdll.dll. Nevertheless, these are crashes that shouldnât be happening, and a new machine shouldnât have a reliability score that low.
For those of you who suspect you have done nothing wrong, that your computer has always worked till recently, and you practise pretty good computer maintenance, your gutâs probably right. The bugs arenât your fault, but that of slapdash, unchecked programming. I doubt you need full reinstallations. You may, however, have to put up with the bugs till a patch is released. It is the folly of getting an update too earlyâa lesson that was very tough to relearn this summer.
Now that I’ve gone four days without a BSOD, it does appear Microsoft realized it had rolled out another lemon, and, nearly two months later, patched things. Goodness knows how many hours it has cost people worldwideâthe forums have a lot of people reporting BSODs (maybe it’s confirmation bias, but I really don’t remember this many, ever). I posted this in a discussion entitled âWindows 10 is a nightmare!’, and the comments there make for sobering reading. A small number have had to purchase new computers; others report that the OS has made their computers unusable or that countless hours were spent trying to fix things. I can believe it. My addition:
I have to concur with the original poster: Windows 10 has been, hands-down, the most shockingly unreliable OS ever made, by anyone, anywhere.
I have spent more time here for this OS than at any other time with Microsoft productsâand Windows 10 has been terrible from day one.
Most recently, I have had multiple BSODs per day since the fall Creators update was installed, and until Microsoft rolled out a patch at the end of January that finally fixed problems of its own making. If your computer is BSODing multiple times a day, with 800-plus events in the reliability monitor per week, then you can imagine how little work gets done. Things finally calmed down on February 2, when I received the cumulative update. You can see the thread for yourself here: I actually feel sorry for the MS tech who stepped in, because heâs solving problems a crap product with faults not of his own making. They wonât be bugs that are in his handbook. Looking at this part of the forum alone, BSOD comes up a lot in the subject lines, more than I ever remember. So it isnât us, Microsoft, itâs you.
Going right back to day one, I canât believe how many threads Iâm involved in. Windows 10 started up differently each day, as it would forget its own settings each day. Some days Cortana worked, other days it didnât. Sometimes I had the UK keyboard (which I had never once installed), other days the US. In November 2015 I had to post a queryto ask how many hours it would take for a Windows 10 machine to shut down. Thatâs right, hours. At least thatâs better than some of you who commented earlier who canât get yours to start up.
Initially, Cortana required fiddling with each day to get it to work. Notifications once went back in timeâon a Saturday I began getting notifications from the previous Thursday. None from Friday though, they all vanished. Windows began forgetting my default browser and default PDF application, and no, you couldnât fix either from the standard settings. The Anniversary update took 11 attempts to install on this PCâand one of them screwed things up so badly my PC was bricked and wound up at the shop, where I had to spend money to get it fixed urgently. (I joked at the time it was called Windows 10 because you needed more than 10 attempts to do anything.) It never installed on my laptop at all: by the time Creators spring came round, the one update that was compatible with my laptop, it had been through 40 unsuccessful update cycles.
Thereâs still more that I can share, and you can probably find it via my profile. I would add more but on the original reply I actually hit a limit on these boxes. I guess Microsoft has a limit to how much bad news it can take from one user.
Microsoft has actually changed its QC procedures for the worseâthat is a matter of recordâand youâd think after three years of abject failure they would switch back. We see the same hackneyed official responses here day in, day out. They need to spend more time getting things right before they ship their OSs, and spare their community people a lot of wasted hours with solutions that generally do not work. In my latest thread, I fixed itâyes, the tech helped a bit, but ultimately I had to listen to my gut and believe that MS had messed up. I was right, but wow, at a massive cost to my real job with days lost to being Microsoftâs unpaid technician.
It is good, however, to come out the other side (knock on wood)âand despite the countless hours spent, I was once again right, and conventional wisdom was wrong. I’m not sure if that’s something to be that proud of. A healthy mistrust of big firms stands one in good stead nevertheless, and remember, every industry has thick people making stuff.
I wonder if we have finally got there with Windows 10âs many BSOD crashes.
Since my last post on the subject in late January, I have had a few more BSODs, but (knock on wood) things have been more stable for a few days. Then again, I haven’t pushed the computer quite as much. Here’s how the Reliability Monitor is looking:
Changes since my last post included adding lines to eudora.ini to switch Quicktime off, which seems to have stabilized that program, and brought the number of appcrash crash messages down.
However, when I did get a BSOD a few days ago, it looked like this (again after using Explorer):
The memory dump revealed nothing new; it was the same as the one I saw when all this began (as far as I can make out).
The big change seemed to have happened after I installed the Intel chipsets, and the number of crashes reduced from dozens to between seven and ten.
I don’t think I have got to an absolute cure yet, but we are getting closer.
The cumulative Windows update (KB4058258) released a couple of days ago may have helped, tooâif it did, it showed that Microsoft had released a lemon with the fall Creators update and rushed to fix things. The number of fixes during the month of January alone suggested that they knew that the OS was iffy. That update was installed yesterday.
Microsoft should rename Windowsâ Reliability Monitor to Unreliability Monitor.
This isn’t too unusual for Windows 10, is it?
I’ve put Oracle Virtualbox and Cyberlink Power2Go back on, because it’s becoming more apparent that Windows 10 is incompatible with my hard drives in certain circumstances. It’s always when a drive (including a phone set up as a drive) is accessed that the system BSODs. It may also be a USB incompatibility. To be on the safe side, I have unplugged one of the two external drives I use.
The Microsoft technician has finally given up and asked I do a clean install. As if I have the timeâthe last time I did that was on an Imac: it took days to get all the OS X updates and the software up and running again. Bwv848 at Bleeping Computer is, like me, determined. I’ll do a memtest (their latest suggestion) when I get a chance.
Just another day using Windows 10 then.
PS.: Since the post: as my settings window would not come up (another fault of Creators fall), I deleted everything out of C:\Users\[username]\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe. That was solved. I also went to Intel to download SetupChipset.exe. Not saying these are solutions to the original cause, and I was largely away from the computer for Sunday. However, I have a real suspicion that, because the computer often BSODs when Explorer (or something relying up on it) is open, there are hard-drive drivers that are failing despite, according to Device Manager, being up to date. One of the modules regularly affected is ntdll.dll, something the Reliability Monitor revealed.âJY
It’s fast becoming apparent that Windows 10âs fall Creators update is a lemon, just like the original Windows 10.
As those of you who have followed my posts know, my PC began BSODing multiple times daily, on average. There were brief interludes (it went for three days without a BSOD once, and yesterday it only BSODed once) but these (now) anomalies don’t really diminish my ‘three to six per day’ claim I made earlier by much.
And it’s all to do with drivers. I won’t repeat earlier posts but the result was that drivers that came with Mozy, McAfee, Malwarebytes and Oracle Virtualbox caused these. In Mozy’s case, it was an old one. Same with McAfee, the remnants of a program that even their removal tool could not take out. Malwarebytes didn’t even show up in the installed programs’ list, and required another program. In Virtualbox’s case, there were both old and new drivers. They all had to be removed, in most cases manually, because removal procedures don’t seem to take them out. This is a failing, I believe.
But with all these drivers gone, I still had a BSOD this morning. Four before lunch. The culprit this time was a CLVirtualDrive.sys driver that came with Cyberlink Power2Go, which came bundled when I replaced by DVD burner last year.
And Cyberlink knows something is wrong with this driver. On December 13, two days after I began getting BSODs, it issued a patch for its latest version. Of course, it leaves those of us with older versions in the lurch, and I was surprised to find that the one it had issued for mine (years old) wouldn’t even run because I was on a bundled OEM edition.
I’m crying foul. If your program is causing BSODs, then I feel it’s your responsibility to help us out. It shouldn’t matter if it’s a trial version, because this is a window into your business. This signals that Cyberlink doesn’t really want to offer a simple download to prevent users from losing hours each day to fixing their computers, even when they’re partly to blame for the problems.
Let me say this publicly now: if any of our fonts cause system crashes like this, contact me and I will provide you with fresh copies with which you can upgrade your computer.
I’m removing Power2Go as I write. It’s superfluous anyway: I only use it because it came as part of the bundle. Windows’ default burning works well enough for me.
But there’s one thing that Cyberlink’s pages have confirmed: the fall Creators update has problems and it seems to me that it is incompatible with many earlier Windows drivers. We can lay a lot of these problems at Microsoft’s feet. Indeed, based on my experience, you could go far as to say that Windows 10 is now incompatible with many Windows programs.
That’s all well and good if you have a new computer and the latest software, but what of those of us with older ones who will, invariably, have older drivers or upgraded from older systems?
Are we now reaching an era where computing is divided between the haves and have-nots? It’s not as though decent new computers at the shops have got any cheaper of late.
Two very helpful peopleâbwv848 at Bleeping Computer and Sumit Dhiman at Microsoftâhave taken me through the steps to figure out what was going on with my Windows 10 desktop computer, on which I’ve had between 100 and 200 BSODs since the Windows 10 Creators fall update arrived.
Windows claimed that the error was a DRIVER_IRQL_NOT_LESS_OR_EQUAL in tcpip.sys, but we know that that wasn’t the cause of the crash.
They had both got to the point where the Driver Verifier had to be run again. On the first attempt, the process had identified an Avira driver, although after removing and reinstalling the anti-virus program, the crashes continued. I had found other dodgy things in the Event Viewer, but solving them didn’t get rid of the BSODs.
Now that I’m back from holidayâand with Windows 10 crashing one more time and costing me more work that hadn’t been backed upâI gave Driver Verifier one more go.
I had been averse to it because of the crashes that resulted from it, and had a sense it would tell me the same thing it had in December.
True to form, Windows wouldn’t even load and it BSODed during the boot. But this time, running Windbg on the dump file revealed something called mobk.sys (Mozy Change Monitor Filter Driver), part of a program called Mozy.
I’ve never heard of Mozy, but it appears to be a back-up program. Checking my driver, it dates from April 2010 and was installed in 2012âaround the time I bought the computer.
It could well have been installed by me as part of a bundle, or by PB (the retailer).
Mozy wasn’t helpful. They have a forum, but when you sign up to use it, you get to a page where they want to charge you US$109 for one of their plans. Personally, if I was making software, I’d want reports from people like me. It’s not as though the question was complex: I wanted to know if it made sense to delete the offending driver in safe mode, or maybe download a trial version of their program, then remove it, in the hope that the driver would be overwritten and deleted. It’s only been a couple of hours since I Tweeted them, so I don’t expect any replies till tomorrow.
Rather than wait, I popped into safe mode and deleted mobk.sys from the system32\drivers folder.
These errors are deeply frustrating and in direct contrast to the stability that my Imacs have exhibited. Even though I’ve tired of OS X, at least I wasn’t losing work because of three to six BSODs per day.
The advice I can give to others is to create a system restore point, then run the Driver Verifier, and repeat the two processes until a culprit has been identified.
There are a few silver linings to this: I got rid of certain software which might have been insecure, and the random resets were quite handy in “clearing” the PC sometimes when I was doing work on it remotely.
I wonder what had changed in Windows between the spring and fall Creators updates that generated this very serious problem. I haven’t seen Windows crash this often since a dying laptop, on Vista, needed a fresh OS installation (it now runs Ubuntu). I’m still of the mind that Microsoft shipped a lemon, given that I’ve had no end of problems with this OS since it launched, from inconsistent behaviour (Windows 10 would originally be different each time it booted up, from Cortana settings to which keyboard it believed I was using), to very difficult updates (Anniversary took 11 attempts on this PC and never made it on to my laptop even after 40 attempts; it only updated to Creators because all other updates would fail).
While I can understand that there was no way either Mozy or Microsoft could have checked on a 2010 driver for compatibility, and there are so many configurations of Windows out there, there’s still no escaping that Windows 10 could have shipped with fewer bugs. Happily, as it turned out, the troubleshooting procedures may have worked, even if things wound up taking a month.
I’ll blog again if I’m wrong about Mozy.
PS. (January 18): After 24-plus hours with no crashes, I got another one, with the same message. Following my own advice, I ran the driver verifier again. Windbg pointed this time to Oracle Virtualbox. I intentionally ran an older version of this because since 2015, no newer version would work due to its hardening feature. Faced with no choice but to update, it had the same error which, finally, I traced to Mactype. This was the error, for those searching:
The virtual machine ‘Windows XP’ has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in ‘C:\Users\User\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log’.
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
The key is to insert these three lines into Mactype.ini:
[UnloadDll]
VirtualBox.exe
VBoxSvc.exe
The error also picked up that there were McAfee drivers left behind from what should have been a full removal. I ran mcpr.exe, found in a thread with the ever-helpful Peter (Exbrit on the McAfee forums). Mcpr.exe did not remove the three drivers, so I took them out manually (despite this going against expert advice): mfeclnrk.sys, mfencbdc.sys and mfencrk.sys. There was also a driver from Malwarebytes, which I downloaded after expert advice in the wake of the damage done by Facebook and its forced download in 2016. Malwarebytes had to be removed with a program called mb-clean as it didn’t show up in the Windows 10 programs’ list.
One important point: when the system restored itself after the latest crash, it appeared the old mobk.sys reinstalled itself into system32\drivers. I removed it again in safe mode. I’ve since created multiple restore points so hopefully none of the now-removed drivers resurface to cause problems again.
I am very happy that I’m running the latest Virtualbox, too, since posting in 2015 resulted in no solid leads. It’s why I’m posting all of this stuff, in the hope others find it useful.âJY
P.PS. (January 22): No crashes for three days, I update both the Microsoft and Bleeping Computer threads with the good news, and within nine minutes, bam! Oracle VM Virtualbox is to blame again, if the driver verifier is accurate. That was yesterday. Today, I attempted to remove the program from the Windows Control Panel. Merely removing it caused three BSODs for three attempts, literally within minutes of each other. I booted into safe mode once, tried to remove it (I couldn’t), then back to the regular mode. I was then able to remove Virtualbox. I have since reinstalled itâlet’s see what happens next.âJY
P.P.PS. (January 23): Two BSODs this afternoon, still so very disappointed software is this unreliable today. Removing a networking driver from Virtualbox has made no difference. Same error as before. I haven’t re-run driver verifier, but I have now updated MacType to the latest version and double-checked the ini file changes are still there.âJY
P.P.P.PS. (January 24): MacType update did nothing. Bwv848 recommends removing Oracle Virtualbox altogether. I may have to do that, and reinstall it only when I need it, and see what happens. Sumit at Microsoft has given up for the time being.âJY
P.P.P.P.PS. (January 25): After one more crash despite some tweaking of the power options last night, I removed Oracle Virtualbox this morning. There were five remaining drivers that removal did not address, two from the latest version (VBoxNetAdp6.sys and VBoxNetLwf.sys) and three from the old one (VBoxNetAdp.sys, VBoxNetFlt.sys and VBoxUSB.sys). I manually removed them. No crashes since, though I will be interested to know if reinstalling, without any of the old drivers present, will make a difference.âJY
P.P.P.P.P.PS. (January 26): Got to its first crash by 11.45 a.m. Driver verifier now blames CLVirtualDrive.sys. Found one user on Virtualbox’s forum who had the DRIVER_IRQL_NOT_LESS_OR_EQUAL crash but the mod doesn’t like me helping out (very protective people, who don’t like their favourite software criticized). A system restore saw Oracle Virtualbox return, even though I made a restore point long after I deleted it. Let’s see what CLVirtualDrive.sys is. Four BSODs before noon. Man from Mozy got back to meâthe first contact other than on Twitterâbecause they wound up spamming me and never responded to my original support question. Amazing how a few eventsâincluding Facebook’s forced download in 2016âhave directly led to this time-wasting point in 2018.âJY
Many years ago, I was locked out of Facebook for 69 hours. It was completely a Facebook database problem, but in those days, they just locked you out without any explanation. It happened on a Friday. I believed I would not get back in till Facebook staff got back to work on Mondayâand I was right. This is a company that seems to close down for the weekend, and the important techs don’t get back till afterwards. It also doesn’t understand the concept of time zones, as six years ago, Facebook walls stopped working on the 1st of each month in every time zone ahead of Pacific Standard Time.
As it’s the weekend before the Gregorian New Year, Facebook’s probably closed again, so if their databases mess up, you could be stuck till Monday. Maybe later.
Except these days, I believe they run another con altogether, as I explained in 2016.
The theory: they now shift the blame to their users, by saying their computers are infected with malware, and forcing a malware scanner download on us. No one knows what this scanner actually does, but I know first-hand that it wrecks your real anti-virus program. I know first-hand that when Facebook and its scanner providers (which once included Kaspersky) are questioned on it, they clam up or they delete comments. I also know for a fact that others can log in to their Facebook accounts on the same “infected” PCs. All this is in earlier posts.
Some affected users over the last few years have said that they could wait this out, and three days seem to be the standard period (though some were out for a month). That sounds awfully close to 69 hours, which I was out for in 2014.
If word got out that their databases were this fragile, their share price would tumble.
In a year when Apple has had to apologize for short battery life on their Iphones, and sexual predators in Hollywood got outed, maybe we could finish off 2017 with Facebook having to apologize for lying to its users about just what this scanner does. Because we also know that people who have legitimate malware scannersâincluding ones supplied by Facebook’s “partners”âhave usually reported their PCs were clean.
Today is the day of the perfect storm: if there is a big database outage at Facebook, it’s the weekend, and no one is around to fix it. For whatever reason, thousands of people have been receiving Facebook’s malware-scan message, telling them their computers are infected: today has seen the biggest spike ever in users getting this, beginning 14 hours ago.
In my two years following this bug, I haven’t noticed any real common thread between affected users.
With Facebook’s old bug, where walls stopped working on the 1st of each month, there was a particularly noticeable rise in reports on Getsatisfaction when 2011 ticked over to 2012âprobably because no one was at work at Facebook to switch 2011 over to 2012. (I wonder if it had to be done manually. It honestly wouldn’t surprise me.)
While some of this is admittedly guesswork, because none of the companies involved are saying a thing, there are just too many coincidences.
Let’s sum up again.
⢠When certain Facebook accounts died three to four years ago, you were locked out, and this took roughly three days to fix (in my case, I got hit at a weekend, so nothing happened till Monday after a Friday bug). These bugs were account-specific.
⢠On January 1, 2012, Facebook walls around the world stopped working and would not show any entries from the new dayâtill it became January 1, 2012 in California, 21 hours behind the first group of people affected. It seems there is some manual tinkering that needs to go on with Facebook.
⢠Today, Facebook accuses people of having malware on their systems and demands they download a scanner. Yet we also know that others can log in to their Facebook accounts on the same “infected” machines. Conclusion: those computers are probably not infected as the lock-outs are account-specific. If it’s account-specific, then that leads me to believe it’s a database relating to that person.
⢠When people refuse to download Facebook’s scanner, many of their accounts come back online afterâyou guessed itâthree days. Ergo, they were probably never infected: Facebook lied to them.
⢠Those that do download the scanner cannot find it in their installed programs’ lists. Neither Facebook nor their scanner partners have ever come clean about what this program actually does or why it needs to reside in a hidden directory on Windows.
⢠It is December 30, 2017, and it’s a weekend, and there’s a spike in users getting this warning. It began, noticeably, 14 hours ago. It’s very hard to believe so many got infected at the same time by the same bug: even a regular virus, or the real malware that gets spread through Facebook, doesn’t have this pattern. It all points back to something happening on Facebook. My reckoning is that this won’t be fixed till January 1, 2018 or afterwards.
⢠Facebook is the home of fake accountsâit’s very easy to find bots and spammers. Logically, if resources are used to host the bots, then that means fewer resources for the rest of us, and potential database problems.
If you are stuck, I recommend you read the postscripts and relevant comments to my earlier posts: here and here.
