Posted on 07/05/2020 8:15:21 AM PDT by dayglored
Microsoft emits a fix for those fearful of Registry tinkering
While Microsoft was showing off its new OneDrive toys, the company also slipped out a fix for brave souls running Windows 10 2004 and finding Files On-Demand a little borked.
Issues have been rumbling for a few weeks now as users of the new OS began complaining that "OneDrive cannot connect to Windows", rendering the Files On-Demand feature, which pulls data down from the cloudy bit barn when needed, broken.
Some found that a Registry tweak would bring the process back to life. Others continued to struggle.
Microsoft pointed to devices or apps that use legacy file system filter drivers as the culprit, leaving some machines unable to connect to OneDrive via the OneDrive app. The afflicted were unable to download new files or open previously synced files - thus somewhat undermining the point.
Some users took the proffered option to simply download all files from OneDrive, but several found even that process hopelessly broken.
For those not keen on the manual workaround of fiddling with the Registry and restarting for each account, Microsoft has put out a troubleshooter to restore access to Files On-Demand. Imaginatively titled "Files On-Demand troubleshooter", the app will run automatically for some users. For others, it will need to be manually started (again for every account) and, after a restart, Files On-Demand should work once again.
The issue affects both the Personal and Business versions of the OneDrive client under Windows 10 2004, although files can still be uploaded and downloaded via the web interface for the storage service.
"Microsoft is working on a resolution and will provide an update in an upcoming release," the company said on its support page for the matter.
The problem does not appear in Microsoft's health dashboard for Windows 10 2004, although users began complaining shortly after the OS was released.
It isn't the only issue with the OS update. Problems persist with Windows 10 2004 more than a month following its release and include difficulties with Bluetooth, and a stop error when plugging or unplugging a Thunderbolt dock. ®
My sentiments exactly!
Think of it this way. Hackers have successfully breached the US Military, other government agencies that included social security numbers, credit report agencies and on and on. Then we have government back doors into various little goodies, including W10.
With all of the above in mind, just why would a cloud be safe?
It’s just duuuuummmmb. If you store your own data you have full control over it. If your data is physically disconnected from the internet/intranet you know it is safe from others unless the drives are physically stolen.
Another item of full blown stupidy is the trend towards one password fits all.
I love these Windows 10 threads. It makes me feel so much better when I crank up my Windows 7 systems.
That's quite interesting, thanks!
Excellent, and congrats on the successful fix.
I liked my Win 7 Pro PC a lot and did so for six years. But there was no way I was going to sign into any of our financial or health accounts with an unsecured Win 7 computer. I forced myself to Win 10 for that reason, battling issues described in this thread.
But I have also have a couple of computers with Linux Mint installed that I use from time-to-time, and one of them is used by my wife when she wants to access an important account. Just another step to remove our dependence on Microsoft.
The overwhelming majority of resolutions for this type of issue lie in third party hooks into the network subsystem. If you're using Win10 and installing any sort of antivirus, third-party firewall, or antimalware suite, I'd bet the farm they're causing your issues.
If it's not third party software, then it's a driver issue with your NIC. Microsoft's driver library is quite comprehensive, but legacy NICs, ESPECIALLY Broadcom adapters, are hit or miss.
The ChiComs thank you for allowing them a foothold into American computers.
You’re welcome. 0patch is unique in that they patch applications running in memory. Slick trick.
MSFT= Bring your own security. See past posts. :)
I think the article gives you pretty much an accurate flavor of how w10 is.
You could try “shut up 10” or registry life” or “spybot search and destroy 1.6.2” (Major geeks.com)
Run Ccleaner every session. (Piriform.com.)
All free. You’re welcome!
You are right, dayglored. CatOwner: the fix is typically updating your wireless network drivers (assuming you are not using a wired connection to your router). Also check for updates to your router firmware... I had to do this to a new HP Computer Win 10 system I purchased last November when my old Win 7 finally died.
> The ChiComs thank you for allowing them a foothold into American computers.
Caveat: We all recognize that, although Win7 can still be useful as a strictly offline old-application platform, going online with it is begging to get pwned.
That said, I anticipated a flood of Win7-specific exploits based on the Win10 security updates released since Win7 EOL. I figured with all the dire warnings prior to Jan 2020, the tech sites would be trumpeting every possible in-the-wild event after Jan.
Rarestia: Honest question: What did I overlook? There are millions if not tens-of-millions of unpatched Win7 systems still hitting the internet. Where’s the flood? Did all the Bad Guys take a break during lockdown? (That’s /sarc, I know they didn’t — if anything they cranked up...)
Why doesn’t Windows read the Tea Leaves and just do this?
They, from it’s release have tried to force Win 10 down our throats, like it or not.
Sorry Windows, I will not comply... Reason Enough...
I’m moving on in a different direction... Sheeple “Carry On... But Wear a Mask while you do it”
You didn't overlook anything. It's an issue of reporting. I'm a cybersecurity engineer, and I can assure you that Win7 has been a prickly thorn over the last 6 months. I've seen one small-scale compromise of a mid-sized manufacturing company due to unpatched Win7 machines.
Win7 as a platform is not necessarily the problem. The most common compromise vector is unpatched machines, regardless of platform. While Windows is a common target, esp. in enterprises, I've seen Linux and even Macs act as beachheads for attackers due to poor patch management.
Windows platforms are useful for lateral movement in an enterprise. The attackers fish some low level employees and can move around with little fanfare once they're inside.
Linux platforms are useful for credential harvesting. I can't tell you how many times I've seen an Apache server compromised due to either poor patch management or cleartext credentials stored in some config file. I know this isn't going to be a popular opinion, but I've found that most Linux admins are lazy. They think because they're on Linux that they can't be hacked, and they don't protect credentials in syslogs or even put privileged account credentials right into a CRON job. This seldom ends well, and I sort of enjoy the looks on the faces of CISOs and security managers when they find out Oracle DBs were compromised due to a lazy admin.
Macs are often compromised through browser addins, but a few years ago I saw a compromise we traced back to a Mac user who downloaded an infected movie from a Torrent on their home network, transferred it to their Mac, connected the Mac to the corporate VPN, and the worm was able to spider out into their network.
Bottom line: Win7 is functional, yes. But as cryptography and security practices advance, the platform will be left behind with no support, and the bad guys are counting on people to continue using those platforms. In-the-wild exploits are often attacked within 48 hours of publishing. No amount of firewalling or antivirus is going to protect them.
...do you refuse to update your phone as well? You have any IoT devices in your house? How about an Echo or a Google device? Those are updated frequently. But you want to control the updates on your computer and complain when a critical security patch is forced on to it?
I’d guess you’d be far more pissed off if your system or home network was compromised because of an unpatched exploit, so Microsoft’s screwed either way in your opinion.
Your opinion is noted. However, my decades of cybersecurity industry experience, security certifications, and job title indicate otherwise.
You’re afraid, I get it. You don’t like being told when you’re doing something wrong. I don’t care what you think about me as a person or my “opinions,” but please, for the sake of your data, get off of Win7. I don’t even care if you go to a modern Linux distro or a Mac, just please STOP using Win7. It’s not if, but when.
Sorry, went down a Win7 rabbit hole and realized you were griping about Win10 updates not Win7.
My previous points stand: if you value your security and the integrity of your data, it’s best you update Windows when you’re prompted. If nothing else, allow critical and security updates. If you don’t want to update subcomponents, that’s your choice.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.