Are NAS Drives Safe Enough to Use in 2024?

Are you a NAS owner? Perhaps you are considering buying a NAS based on a recommendation from a friend, work colleague, IT professional or even myself (Robbie) on YouTube. The appeal of owning your own server, cutting the connection with your subscription cloud providers such as Dropbox or Google drive, having all your data backed up in-house and that feeling of pure control/ownership is hard to underestimate. However, over the last 4-5 years or more, it has been hard to ignore that the brand has suffered a series of security issues surrounding the subject of ransomware – a process whereby your data is encrypted with a unique, near uncrackable cypher and a document (typically a .txt) is left for you with instructions for you to make a payment in bitcoin to a predesignated account in order for instructions and the key to recovery your data. Ransomware in of itself is not new and originally dates back to 1996 under the name cryptoviral extortion (you didn’t come here for a history lesson, but the wiki covers a lot of those early developments into the concept) and is frighteningly easy to conduct IF an intruder has access to your system and/or the means to inject the command to encrypt the data inside of any system. Words like virus, hack and malware have been thrown around the internet for the last 20-30 years, however, Malware feels significantly more organized and comparatively recent, as well as being something that has been enacted on all storage platforms, such as Google Drive (thanks to sync tools), Apple was directly hit in 2021 and over 300 BIG name companies that you WILL of heard of in the last 18 months that included:

Acer, FujiFilm, Northern UK Rail, Exabyte Web Hosting, Foxtons, The Salvation Army, Shutterfly Photography, Bose Sound, The NRA, Kronos CRM systems, Gigabyte Motherboards, Volvo, SPAR, Olympus Cameras, GUESS Fashion, ADATA, CD Projekt, Travelex, SK Hynix, Capcom, Crytek, Kmart

Those are just a brief scan of confirmed news reports and only a small fraction of the companies, brands and institutions that have been successfully targetted. Tech companies, media companies, charities and countless retail outlets. Why am I going through all this? Well, 1, these companies should have exceptionally sophisticated storage and remote access protocols in place, 2, cannot use the excuse of being companies with practically no formal association with high-level storage and 3, are companies with a responsibility to protect significantly custom databases that eventually fell foul (partially or fully) to vulnerabilities. Personally, I DO think, when NAS brands have blame on their side (eg Asustor/Terramaster with Deadbolt, QNAP with QLocker, Synology with SynoLocker, etc) that they need to acknowledge publically, make significant errors in these attack proactive management AND have handled a number of the follow-up actions to these incidents very poorly (both in terms of communication and execution) – They need to put their hands up and say “We F’d Up” and take responsibility, up to a point! However, I do also think that the end-user base is also not completely innocent and alongside ascertaining whether any particular NAS brand is safe to use in 2024, we should also think about how we store data, the limits of our own due diligence and our expectations from server devices.

Important note – If you are currently unaware of the severity of ransomware attacks, malware attacks and authentication bypass vulnerabilities, you need to subscribe to this page HERE on NASCompares. Also, if yo are in any doubt about NAS security and owning a system, REMEMBER, the very LEAST you can do is:

• Set your system software updates to automatic (either FULL or just security updates)
• Disable the ‘admin’ account (it should be disabled by default, but make sure!)
• Disable SSH / Terminal services if you are not using them (again, these should be ‘off’ by default, but check)
• Create exclusre login credentials to services/clients (eg Plex should/can have a user:plex + password, and then restrict that account to only the folders and services that it needs, then restrict or ‘ready only’ the rest
• Have at least one backup in place. Remember that a backup is a complete copy of all your data in a different system/location!!!
• Change random ports in the system for accessing the NAS (you tend to find NAS systems use 8000, 8001, 8080, 5000, etc. Change them to something random)
• Enable 2 Step Authentication / 2FA / OTP
• Do not F&*k around with your router or open ports unless you know what you are doing!

Additionally, if you have been affected by ransomware on your storage solution (QNAP, Synology, UnRAID or whatever brand), this post is not intended to play ‘blame games’ or detract from the impact (personally or professionally) that it has caused. I have experienced ransomware attacks, malware attacks through my browser, virus attacks on my OS and seen my fair share of attacks fail and (annoying) succeed. Please do not take this article in the spirit of ‘get stuffed, It’s your fault!”, but as a means of dissecting the current state of play with NAS devices and the realistic expectations/responsibilities of all involved.

PSA – GET YOUR BACKUPS IN ORDER!

Before you even go one paragraph further, I have a simple question for you – do you have a backup in place? If yes, then carry on to the next part. If not, and I cannot stress this enough, GET ONE NOW. The time you are spending reading this you could be susceptible to data loss in about 10 different ways without even factoring in ransomware (Power failure leading to hard drive corruption, Malware from a slightly iffy google search this morning, cloud storage provider going bust, OS failure on your device, etc). In this day and age owning a sufficient data backup is as sensible as buying a raincoat or looking both ways when you cross the street – you don’t do it because you like rain or like looking at cars, you do it because they are peace of mind, they are a safety net, they are for caution in case of the worst. It is a bit tenuous, but owning one or multiple backups always make me think of this quote from Shawshank Redemption by Stephen King:

“There are really only two types of men in the world when it comes to bad trouble,” Andy said, cupping a match between his hands and lighting a cigarette. “Suppose there was a house full of rare paintings and sculptures and fine old antiques, Red? And suppose the guy who owned the house heard that there was a monster of a hurricane headed right at it. One of those two kinds of men just hopes for the best. The hurricane will change course, he says to himself. No right-thinking hurricane would ever dare wipe out all these Rembrandts, my two Degas horses, my Jackson Pollocks and my Paul Klees. Furthermore, God wouldn’t allow it. And if worst comes to worst, they’re insured. That’s one sort of man. The other sort just assumes that hurricane is going to tear right through the middle of his house. If the weather bureau says the hurricane just changed course, this guy assumes it’ll change back in order to put his house on ground zero again. This second type of guy knows there’s no harm in hoping for the best as long as you’re prepared for the worst.” 

Get a Backup in place

More Ransomware Attacks on QNAP than Any other NAS Brand?

WannaCry, QLocker, eChoraix, Deadbolt, how, many, times…

Probably the most compelling argument against the safety of NAS for many buyers is the simple fact that NAS brands increasingly seem to been in the news more for reasons of ransomware attacks. Indeed, even a quick browse of the last 24 months on the site ‘Bleeping Computer’ for stories on QNAP shows you that there have been multiple vulnerabilities found in their software/access that have allowed encryption commands to be injected into the QNAP NAS system to execute the ransomware attacks. How can this one brand be such a soft target? What are they doing wrong? Well as it stands, reading through news posts before/after previous ransomware attacks, as well as the dissection of events on the official forums in the midst of the an attack, the consistent threads are:

• QNAP is rolling out software and services with weak default settings and acceptable minimums to allow inexperienced users to open up external access WITHOUT the users understanding the risks
• QNAP has weaknesses in it’s software that the brand arguably takes a more reactive, than proactive stance on repairing
• QNAP’s recommendations on actions to user post-ransomware attack both publically and in 1-to-1 dialogue with users has been felt unsatisfactory
• Your QNAP NAS is better off currently used offline/network only

As general as all that might sound (without letting personal opinions colour it) those are largely the four core issues for many that have voiced their feelings on this in the forums. Moving away from the hefty subject of data loss slightly (we will be returning to that in a bit, but that is a question of Backups and routines to discuss), there is the fact that there have been vulnerabilities found in QNAP 1st party applications and services – but then again, so have there been in different NAS brand’s own services too. A click look at their respective Security Advisory pages will tell you this. This doesn’t exonerate QNAP in any way here, as part of the ‘social agreement’ between the end-user and QNAP is that as long as we ‘follow due diligence in protecting the data inside the NAS as directed AND maintain our own network/router setup, the QNAP NAS should protect our data inside the NAS to the best of it’s ability. This is where it all becomes problematic. As QNAP have never successfully balanced the line between giving the user freedom, control and customization WHILST still preventing the user from doing anything self-harming without a full idea of the consequences. It’s a line that their biggest competitor Synology seems to toe better and this comparison only serves to re-enforce the feeling (and numbers) that QNAP are attacked more.

The Nature and Practice of Firmware Updates on ALL NAS Brand Devices – Prevention & Cures

“Remind me Tomorrow” click

Though sometimes NOT the means with which a vulnerability in the NAS software/services is achieved, it is still a factor in some instances that updating to a later firmware would actually have closed a vulnerability. However, this is a remarkably broad statement and the truth is a great deal more nuanced. First, we have to understand that ALL software that has a remote access component via the internet will likely be investigated by cybercriminals for weaknesses. Not just NAS ones – ALL of them, from Microsoft office and Android mobile OS, to your LG TV and Amazon FireTV. Hell, I bet there are people who have investigated the ‘buy now’ option of WINRAR in effort to see if an opening exists to use it as a ransomware entry vector. What I am saying is that as soon as a commercially popular software with internet access exists, people are going to try and take it apart to find out its weaknesses for exploitation. If/When these weaknesses are found and actioned (or submitted to the brand for bounty programs – whereupon brands ask people to try and break their software, so they can make it better/safer/improved), the brand then issues a firmware update to the affected software/services to its user base, then around the merry-go-round we go again! This is not a process that happens daily – but it definitely happens weekly or monthly (depending on the frequency of the brand to instigate the changes that are raised to them). This is why is it so common for companies that are affected by ransomware in their software/services to immediately highlight the need for firmware updates. At that point, the attack vector and vulnerability is reverse engineered, patched and closed. Many of these vulnerabilities are small. Very, VERY small sometimes. Indeed, it is for this reason that all the reputable NAS brands have security advisory pages that list current weaknesses, vulnerabilities and issues on their platform that are being investigated (Synology HERE, Asustor HERE and yes, QNAP HERE) and in all my time in the world of network-attached storage, I do not think I have ever seen one of these pages have ‘100% resolved’, but when something is resolved the resolution is invariably rolled into an update. So what we can take from this is that although firmware updates do not completely remove the possibility of new vulnerabilities being found in the future, they do seemingly close the bulk of existing vulnerabilities that have been found by/volunteered to the brand.

So why do we not install the firmware updates automatically? This isn’t limited to NAS of course! From the Mac notification that have been nagging you at the top right of your screen, to the windows update at the bottom right and all those applications on your phone that are asking you to please install the latest updates to your software – we choose to ignore them til ‘later’! Worse still, there is the old ‘if it ain’t broke, don’t fix it’ mentality that will often result in many users only installing smaller updates, but flat out avoiding the BIG updates as they can ‘change where everything is’ or ‘I heard it breaks a bunch of stuff’. Businesses in particular with shared files in their thousands are always reluctant to run any process that can suspend that access temporarily or change how something works. So, there we have a fine melting pop of ingredients that has led (in some instances, but not all – as we will go further go into) to many users being hit by ransomware attacks via vulnerabilities that, although patches were available, were not actioned. How do we resolve this? Forced update that leaves the user’s own hesitance out of the equation? Limitations of the system’s remote connectivity unless the latest firmware update is installed (console gamers will be very familiar with that method of course)? Or a 50/50 split where minor updates are optional, but larger ones are mandatory? It’s a tough tight rope to walk. So, let’s see how QNAP walked/walks this tight rope and how they could have possibly done it ALOT better.

System Updates and Updates – Should a NAS Brand FORCE Firmware Updates to Users?

Forced? Optional? Access Penalties?

As mentioned, tighter control of firmware implementation would allow the brand to ensure that a NAS that has internet accessibility is updated to a high/current firmware revision. Alternatively, the brand could limit the systems external connectivity and disable all settings if the firmware on the system is not up to date – simply running a check with the NAS brand connected domain when trying to access these services and settings and declining if the latest update is not installed. Xbox and Playstation users are more than aware of this as a fixed rule to ensure that installed software is officially licenced and checked in advance. However, those are closed systems and many buyers have selected NAS over cloud services precisely because of the flexibility and customization it offers. However, when NAS brands have previously FORCED firmware updates remotely for services, it has NOT been received well:

Forced updates are something of a taboo subject too, with the recent rather heavy-handed move by QNAP back in 2020 in light of the Deadbolt ransomware attack to remote push the latest firmware update to all QNAP NAS systems that were internet-connected without any notice to the end-users (overriding any settings that disabled or prevented this). Now, clearly, QNAP did this as an extreme and something to prevent the vulnerability of the system software and/or configuration from being exploited further (that have still not been fully confirmed in its attack vectors, with some users who have ridiculously high-security settings still getting hit). In non-ransomware instances, I think QNAP issuing a message to their user base with a “In 5 day’s there will be an essential system update on XX day XX month at XX:XX time” message, with even a brief explanation of why would have been infinitely more preferable and would have been met with a much more positive stance (as well as it also making many users update sooner). However, clearly, the decision for a forced update was more of a last resort/hastily decided choice and that forms part of another reason that many users find the QNAP platform to sometimes bring services and software to market that could do with a little more time in the oven. Whatever way you look at it, QNAP was going to be damned, whatever they did. But did they put themselves in this position? What about the expectations of the end-user and due diligence? What SHOULD be the expected skillset of a NAS buyer to start with?

The Extent of the End User Responsibility, Skillsets and Expectations? What Are YOUR Responsibilities as a NAS Owner?

How much should a user be expected to know about networking?

The simplicity of NAS systems can often be oversold. It’s annoying and I am as guilty as most of this, but given the wide range of users who install a NAS system into their storage environments, the ease of setup and use is not shared with the ease of setup and understanding of network security in your home or office. On the one hand, NAS brands have supplied multiple services and processes in their system software that make remote access easy, encrypted transmissions easy, SSL certificate applying easy, 2-step authentication easy, UPNP and router pushing easy – you name it, they have tried to make it easy. But should they have? The ease of setting up a number of these services (as well as non-randomized settings in some places) can easily give users a false sense of security. So, for those users of a higher skillset, it would be acceptable that a NAS should only be remotely accessed with the highest layers of security applied, and it should not allow remote level access to be possible without some unique intervention and set-up by the end-user (not just a password and/or disabling an admin account), although to stop presets of this nature would lead to a noticeable spike in the difficulty of setup, perhaps that is what is needed. This is by no means a new issue we are discussing and even a brief google search online finds examples of attack vectors and methods as far back as 1999 on public/org sites.

However, in reality, it simply would not work like this, The user base of most established NAS brands are just too varied and though these tougher and more unique security implementations would secure things, the less technically skilled users would hit hurdle after hurdle, once again, one of the prices of some (not all) of that flexibility. Alot of users who have been hit by ransomware attacks have specifically headed to official forums because they do not have the remote setup experience that might be deemed an acceptable minimum to start opening ports via the NAS settings or directly on the router. This once again brings us back around to what should be the expected skill level of an average NAS Drive owner, how much of the control and security profile of the storage system belongs to the NAS manufacturer and how much should the buyer be expected to do independently? You can buy a car, you can fill it with petrol and the manufacturer can tell you its top speed, and miles to the gallon – but no car manufacturer would feel the need to add to all their adverts “must have a driving licence”, do they? It’s a rather stretched simile I know, but the fact remains that users cannot expect to connect their storage to the internet in 2024, open up pathways to it via the internet and not at least make allowances or provisions that an attack could happen. This leads us to the hardest and coldest fact of practically EVERY SINGLE NAS related recent ransomware attacks that, although only applies to a % of users, is still depressingly true.

How Backups and Data Storage are Still being Misunderstood – UNDERSTANDING WHAT A BACKUP IS, AND A NAS IS NOT!

A frighteningly large number of victims with no backup. Acceptable backup levels?

One of the hardest choices for anyone that has been successfully targetted by ransomware attackers (not exclusive to NAS either) is the choice to pay or not. When I am asked to make recommendations for a home or business user in the free advice section here on NASCompares or the comments on YouTube, I will always ask what the user storage quote is currently (now then double annually over 5yrs), their user base (volume and frequency) and their budget? That last one is always a kicker for some, as no one wants to show their cards! I’m not a salesman and I do not work for a eRetailer, I ask because there is a lot of ground between a £99 DS120j and a £5000 RS3621XS+. However, budget is INCREDIBLY important and should not only be measured by the number of 0’s in the account, but also by the cost of if the data is lost! Many users are so busy thinking of how much it will cost to provision for the future, that they are not factoring in the cost of replacing the past! This is the exact personal vulnerability that ransomware targets and sadly, a lot of users still do not understand 1) what a backup actually IS and 2) what a backup actually ISN’T.

If your data ONLY lives on the NAS, then the NAS is not a backup. You likely knew that. But socially and conventionally, we tend to forget it quite easily. We make space on phones by deleting stuff because ‘it is backed up on the NAS’. We sync our laptops and MacBooks with a remote folder to keep our files safe on the NAS, but still make changes or delete files on the hoof. We take the NAS as red as a backup and at that point, it isn’t! Likewise there are things that SOUND like backups… RAID… Snapshots… Hot Spares… they sound very reassuring, but are not backups, they are safety nets! And are all typically found ‘in system’. A REAL backup is something that is the same files, ELSEWHERE!  There is no avoiding that a NAS (Synology, QNAP, TrueNAS, Whatever!) is NOT a backup solution in of itself, but can be used IN a Backup Strategy. All brands highlight at numerous points on their website that you should have a 1-2-3 Backup strategy, or a bare-metal and cloud backup, or a periodic USB backup, a NAS to NAS remote backup – or ALL of them! Sadly, there are a lot of users in the official NAS branded forums that have been hit by ransomware and did not have backups in place, with some knowledge that they needed a backup but their budget’s prohibited it. Whilst others say that a NAS brand publishes in its online literature that it’s a backup device, they bought it as a backup device, therefore the company missold it and that is the end of argument!

The sad truth is that the brand is not responsible for your backup routine or strategy, it supplies the means to store and access data and their responsibility (succeed or fail) is to ensure its hardware and/or software provides a default secure level of access, as well as the means to configure that access to the users control. There HAVE been vulnerabilities found and they have patched them, as is the usual process in these things (at least, they say they have at that is the best guarantee we can ever have from a brand in the circumstances), but they are NOT responsible for your backup routine. This now leads us to the subject of the NAS hardware, the NAS software and comparisons between brands.

Hardware vs Software Priorities – Is Synology Safer Than QNAP?

Hardware vs Software, QNAP vs Synology, Is the grass greener?

Way back in the mid twenty-teens, whenever I would discuss QNAP and Synology on the platform, I would always say that you go to Synology for the Software and QNAP for the Hardware. Synology’s DSM platform clearly makes up the bulk of the companies investment and attention, makes up a significant chunk of the price tag and is designed around keeping things as user-friendly as possible (within reason). This is why their devices at each generation refresh (DS918+>DS912+>DS923+ or DS218+>DS220+>DS224+) only make smaller increases on the previous generation – the software IS the focus. With QNAP we tend to see the hardware taking bigger leaps each generation. Better standard ethernet, better PCIe gens, Better CPUs much earlier and overall greater hardware at any given time. For PC builders and those that know a lot more about the contents of their laptop than the contents of their router, this is speaking THEIR language and makes the price tag translate better. Fast forward to now and although that logic still remains the same, these brands are more 60/40 in their architecture (where 60 = their preferred hardware or software bias). The issue starts when QNAP seem to rush their software out the door very quickly. Alongside a lot of more beta applications being available, they roll out a lot of new types of software that (and I am sorry to use that expression again, but) could have used more time in the oven. This approach to software development and release can be dicey and although it makes QNAP the more exciting platform (with its better hardware, more diverse software and continued AI or generally automated services), it also means that the platform has less of the layers of troubleshooting red-tape that Synology has (which inversely means the Synology product is going to be more expensive and less hardware rich, as that investment of time needs to be repaid to be justified). In recent years, QNAP has seemingly slowed down it’s hardware releases and rolled out more in software, introducing bounty programs for vulnerabilities, pen testing and is seemingly learning from their mistakes (we hope). Whilst Synology have further doubled down on software innovation, with solutions remaining longer in the market between refreshes) and continued on their path to continued dominance in NAS. Whether you look at the whole thing as a tortoise and the hare situation, or a case of ‘slow and steady wins the race’, there is no denying that Synology appears to take security more seriously than most other brands.

Look at the Apple TV box or Amazon FireTV / Firestick? Is it user-friendly? yes! Is it slick and intuitive? Yes! Is it flexible in the installation of 3rd party applications? NO (at least, not without workarounds)! Is it hardware-powerful? LORD NO! One glance on eBay will show you a thousand other media boxes at the same price with Android on board, 5-10x the hardware and customization coming out of the wazoo. Nevertheless, many users will not buy the apple/amazon media option because although they KNOW it will be slick and ‘hold your hand’ all the way, it will be a closed system, noticeably more expensive and even then “nothing is full proof, right?”. And a lot of the anger at QNAP for their increased ransomware targeting and handling of this needs to also be balanced against why a lot of users chose the QNAP NAS brand. The QNAP NAS platform does have good applications and services, some genuinely unique ones and ones that allow tremendous flexibility and customization – but users need to remain relative to what drew them to the platform and have sufficient backups AND safety nets in place. I would say this about QNAP, about Synology, hell… Google drive, DropBox, Backblaze… ALL of them have localized client tools that rely way too much on the success of versioning/roll-backs being possible on the cloud platform. None of them are 100% full proof and QNAP dropped the ball multiple times here, but none of these ways are unprecedented and should be provisioned for regardless of your NAS brand or cloud platform.

The Sad Truth about Servers, Security and Vulnerabilities

Vulnerability > Update > vulnerability > update > rinse > repeat

No platform, software or service is going to be 100% bulletproof. You can increase your personal layers of security (VPNs, Encryption, layers, restrictive white lists, etc) to hit 99.99% but whatever way you are looking at it, everything we use is software-based and therefore, fallible. Equally, users cannot pretend that it is still the early days of the internet anymore and still be annoyed when a statistical possibility that should have been factored against was not. Do I think NAS drives are safe? I’m sorry to say that the answer is never going to be a simple Yes/No. I think they provide what they say they provide and I think that NAS hardware is still the best in the market right now. But the majority of NAS brand software needs to be less rushed (I somewhat absolve Synology of this, as they seemingly take it 10/10 seriously!), the extra time/budget be spent on that software, or utilize a trusted 3rd party. The need to relinquish some of the customization of their platform in efforts to remove some of the configuration out of the hands of less tech-savvy users who end up overly reliant in defaults. Perhaps a much more rigorous setup policy that, on day 1, have an EXPERT door and a NOVICE door, with randomized defaults and extremely regimented update rules on the latter. Equally, the brand (though better than it was) needs to work on its communication with its end-user base, both in the event of critical issues and education on what the user base needs to have to increase security OUTSIDE of their product.

I still recommend the majority of turnkey NAS brands in the market in terms of their bse product and the range of security/system protection tools they include, but we need to be realistic and honest with ourselves about what we buy and our expectations. If I buy a NAS, I expect it to store the data I store in it and allow me access to it on my terms, but ‘my terms’ might be a lot more/less strict than the next person and with that comes due diligence in 2024. I hope that the last big ransomware attack, deadbolt from the start of 2022, is the last ‘big’ one we hear about moving forward, but I do not think it will be. More than just any one brand, one look at the vulnerabilities listed on security advisories of all the brands tell us that there is big money to be made by these intruders and the brands can only stay 1 step ahead. As always, me and Eddie here on NASCompares have been running a page that links to the bigger NAS security Advisory pages that gets regularly updated, so if you want to get notifications on these as they get added (pulled from the official pages themselves), then you can visit the page below and put your email in for updates when they happen. Have a great week and backup, backup, BACKUP.

Click Below to Read

 

Finally, If you are currently unaware of the Deadbolt ransomware attack that took place on QNAP NAS devices, you can find out more in the NASCompares article and video below:

 

SUBSCRIBE TO OUR NEWSLETTER
[contact-form-7]
Join Inner Circle

This description contains links to Amazon. These links will take you to some of the products mentioned in today's content. As an Amazon Associate, I earn from qualifying purchases. Visit the NASCompares Deal Finder to find the best place to buy this device in your region, based on Service, Support and Reputation - Just Search for your NAS Drive in the Box Below

Need Advice on Data Storage from an Expert?

Finally, for free advice about your setup, just leave a message in the comments below here at NASCompares.com and we will get back to you. Need Help? Where possible (and where appropriate) please provide as much information about your requirements, as then I can arrange the best answer and solution to your needs. Do not worry about your e-mail address being required, it will NOT be used in a mailing list and will NOT be used in any way other than to respond to your enquiry. [contact-form-7] TRY CHAT Terms and Conditions   Alternatively, why not ask me on the ASK NASCompares forum, by clicking the button below. This is a community hub that serves as a place that I can answer your question, chew the fat, share new release information and even get corrections posted. I will always get around to answering ALL queries, but as a one-man operation, I cannot promise speed! So by sharing your query in the ASK NASCompares section below, you can get a better range of solutions and suggestions, alongside my own.

WE LOVE COFFEE

 

Severe D-Link Security Vulnerability Discovered – CVE-2024-3273 and CVE-2024-3274 Hard-Coded Credential Backdoor

The cybersecurity landscape has been significantly impacted by the discovery of two vulnerabilities in D-Link NAS devices, designated as CVE-2024-3273 and CVE-2024-3274. These vulnerabilities affect multiple (approx 92,000 internet facing devices, the bulk of which are UK based) D-Link NAS models that are no longer supported by the manufacturer due to their end-of-life (EOL) status. This detailed analysis aims to unpack the complexities of these vulnerabilities, their operational implications, and the necessary user responses.

Impact and Affected D-Link NAS Model:

The confirmed list of affected D-Link NAS models includes:

Model	Region	Hardware Revision	End of Service Life	Fixed Firmware	Conclusion	Last Updated
DNS-320L	All Regions	All H/W Revisions	05/31/2020	Not Available	Retire & Replace Device	04/01/2024
DNS-325	All Regions	All H/W Revisions	09/01/2017	Not Available	Retire & Replace Device	04/01/2024
DNS-327L	All Regions	All H/W Revisions	05/31/2020	Not Available	Retire & Replace Device	04/01/2024
DNS-340L	All Regions	All H/W Revisions	07/31/2019	Not Available	Retire & Replace Device	04/01/2024

These devices, pivotal in small office/home office (SOHO) environments for data storage and management, are now susceptible to remote attacks that could compromise sensitive data integrity, availability, and confidentiality.

CVE-2024-3273: Command Injection Vulnerability Explained

CVE-2024-3273 exposes a command injection flaw within the web interface of affected D-Link NAS devices. The vulnerability is located in the handling of the system parameter within the nas_sharing.cgi script, which improperly sanitizes user-supplied input. This oversight allows authenticated remote attackers to inject and execute arbitrary shell commands encoded in base64. The execution context of these commands is particularly concerning, as it typically runs under the web server’s privileges, potentially leading to unauthorized access to the system, modification of system settings, or initiation of a denial of service (DoS) attack.

Technical Dive into CVE-2024-3274: Hardcoded Credentials

CVE-2024-3274 reveals a hardcoded credential vulnerability, manifesting as a backdoor account (messagebus) embedded within the device firmware. This account, notably lacking a password, permits unauthenticated remote access to the device’s administrative interface. The presence of such hardcoded credentials significantly lowers the complexity of unauthorized device access, making it a critical vulnerability. This backdoor could be exploited in tandem with CVE-2024-3273 to elevate privileges or gain persistent access to the compromised device.

Who Found the D-Link Vulnerability?

The vulnerabilities were disclosed by a security researcher operating under the pseudonym “netsecfish,” who provided detailed technical insights and proof-of-concept (PoC) code. This disclosure highlighted the risk of widespread exploitation, given the estimated 92,000 devices exposed online across various regions, including the UK, Thailand, Italy, and Germany. The timing of the disclosure, subsequent to the affected models reaching their EOL, exacerbated concerns around feasible mitigation strategies.

You can find the full and very detailed outlining of the Vulnerability and Potential attack vector HERE on Netsecfish’s github listing

Mitigation Strategies for Users Who Are Still Using A D-LInk NAS

In light of D-Link’s stance on not providing firmware updates for EOL products, affected users are faced with limited mitigation options. The primary recommendation is the retirement and replacement of vulnerable devices. Interim measures, for those unable to immediately replace their devices, include isolating the NAS devices from the internet, implementing strict network segmentation, and employing firewall rules to restrict access to the management interface. Additionally, monitoring for unusual network activity can provide early detection of exploitation attempts.

D-Link Official Response

D-Link has acknowledged the vulnerabilities but emphasized the EOL status of the affected models, which precludes official firmware updates or patches. The company has issued advisories urging users to replace outdated devices with supported models. This situation underscores the importance of adhering to device lifecycle policies and maintaining an updated infrastructure to mitigate security risks.

You can see the full official D-Link Response HERE

At the time of writing, there is no mention of this on their social media pages. Hopefully this changes, as the potential 82,000 internet facing units in the wild need to be addressed.

Exploitation in the Wild of the hard-code credential D-Link Vulnerability

GreyNoise, a cybersecurity firm specializing in analyzing internet-wide scan traffic to identify threats, has provided valuable insights into the exploitation attempts of the D-Link NAS vulnerabilities. According to their analysis, a significant uptick in scan activity targeting the specific vulnerabilities CVE-2024-3273 and CVE-2024-3274 was observed shortly after their disclosure. This activity suggests that attackers are actively seeking out vulnerable D-Link NAS devices for exploitation. GreyNoise’s findings indicate that the exploitation attempts are not isolated incidents but part of a broader effort by malicious actors to identify and compromise affected devices. The data collected by GreyNoise highlights the real-world implications of these vulnerabilities and serves as a critical alert for organizations and individuals to take immediate protective actions against potential unauthorized access and exploitation of their D-Link NAS devices.

You can learn more about this on Greynoise’s official page on this matter HERE

The D-Link NAS Series is Still For Sale (Technically)

Despite the end-of-life status and known vulnerabilities of D-Link NAS models DNS-340L, DNS-320L, DNS-327L, and DNS-325, these devices continue to find a marketplace on platforms such as eBay and other online resale venues. This ongoing sale of used units poses a significant cybersecurity risk, as many sellers and buyers may not be fully aware of the devices’ vulnerability to exploits. Alarmingly, at the time of writing, it is reported that over 80,000 of these units remain actively internet-facing, directly exposing them to potential exploitation by attackers leveraging the CVE-2024-3273 and CVE-2024-3274 vulnerabilities. The persistence of these devices in active operational environments underscores the critical need for heightened awareness and proactive measures among current users. Potential buyers should be cautioned against acquiring these models, and existing users are strongly advised to consider secure alternatives that receive current manufacturer support and updates, mitigating the risk of compromise.

I own a Synology/QNAP NAS, Should I Care? How to Automatically Get Updated When Synology and QNAP NAS Vulnerabilities are Reported

Pretty much ALL of the brands in NAS, Data Storage and Cloud services have these security advisory pages, but the idea of checking these pages manually (i.e. bookmark etc) every day, week or month is too much of a hassle for many. On the other hand, they all arrive with an RSS feed link that allows users to subscribe to updates BUT many users are not even aware of how to apply an RSS feed (it’s a complex XML feed of text that needs to be injected into an appropriate RSS feed client/agent – so yeah, hardly noob friendly). So, in order to make this 1000x easier, I have (and by me, I mean Eddie the Web Guy spent time on it and I made this article!) made this page that will be constantly updated with the latest vulnerabilities reported on the popular NAS brands and storage-related manufacturers. It is still being built (so more brands are being added) but it will allow you to just chuck your email address below (will not be used for profit or spamming etc) and then you will get an alter EVERY TIME a new security vulnerability is updated by the brands (this is automated, so it will appear here as soon as it appears on the respective security advisory page). Additionally, there will be links back to the brand/manufacturer site so you can find out more about individual exploits and vulnerabilities, how they work, what they do and (most importantly) give you a better idea of whether you should update your NAS/Storage system or not. I hope you find it helpful and if you have any recommendations or idea of what we should add to this page/service to make it even better – let us know in the comments or directing here – https://nascompares.com/contact-us

Sign Up Below to Get Updates as New Vulnerabilities Are Reported

Find an updated vulnerability list here:

Comprehensive User Recommendations

Beyond immediate mitigation, users should consider several best practices for network device security:

• Conduct regular security audits of network devices.
• Update all devices to the latest firmware versions where possible.
• Employ network firewalls and intrusion detection systems to monitor and control inbound and outbound traffic.
• Practice the principle of least privilege by restricting device access to necessary personnel.

Conclusion

The vulnerabilities identified as CVE-2024-3273 and CVE-2024-3274 in D-Link NAS devices present significant security challenges. The absence of official firmware updates for these EOL products necessitates proactive user measures to mitigate risks. This analysis serves as a call to action for users to evaluate their network security posture critically, implement robust security measures, and ensure that all network-attached storage devices operate within their supported lifecycle.

SUBSCRIBE TO OUR NEWSLETTER
[contact-form-7]
Join Inner Circle

This description contains links to Amazon. These links will take you to some of the products mentioned in today's content. As an Amazon Associate, I earn from qualifying purchases. Visit the NASCompares Deal Finder to find the best place to buy this device in your region, based on Service, Support and Reputation - Just Search for your NAS Drive in the Box Below

Need Advice on Data Storage from an Expert?

Finally, for free advice about your setup, just leave a message in the comments below here at NASCompares.com and we will get back to you. Need Help? Where possible (and where appropriate) please provide as much information about your requirements, as then I can arrange the best answer and solution to your needs. Do not worry about your e-mail address being required, it will NOT be used in a mailing list and will NOT be used in any way other than to respond to your enquiry. [contact-form-7] TRY CHAT Terms and Conditions   Alternatively, why not ask me on the ASK NASCompares forum, by clicking the button below. This is a community hub that serves as a place that I can answer your question, chew the fat, share new release information and even get corrections posted. I will always get around to answering ALL queries, but as a one-man operation, I cannot promise speed! So by sharing your query in the ASK NASCompares section below, you can get a better range of solutions and suggestions, alongside my own.

WE LOVE COFFEE

 

If you have tried to update your computer but cannot install some critical updates, you may get the error message that your device is missing important security and quality fixes. This error may include the 0x80070643 error code.

This error is similar to the 0x8024ce16 Windows update. In this guide, we will walk you through some of the most effective ways of fixing the Windows 11 problem.

1. Run the Windows Update Troubleshooter

On Windows 11, you have several troubleshooters built into the operating system. The Windows Update troubleshooter is one of them. It will scan the computer for potential causes of your device missing important security and quality fixes. It will fix the problem or recommend solutions.

1. Open the Settings app by pressing the Windows + I keys.

2. Click the System option on the left, then click Troubleshoot on the right.

3. Click Other troubleshooters.

4. Click the Run button for Windows Update.

5. Follow the wizard to complete the process, then restart the computer if needed.

2. Reset Windows Update Components

When you encounter the error that your device is missing important security and quality fixes, you should reset Windows update components. This reset will fix corruption or missing files that may contribute to the error.

1. Click the magnifying lens on the Taskbar, type cmd, and hit Run as Administrator.

2. Run the commands below by typing them in the command prompt and hitting Enter after each one. This will stop all update services.

net stop wuauserv

net stop bits

net stop appidsvc

net stop cryptsvc

3. Optionally, delete your temporary files by running the command below:

cd %systemroot%\SoftwareDistribution
del /f /s /q *.*

4. Run both commands below to rename the SoftwareDistribution and Catroot2 folders.

ren %systemroot%\SoftwareDistribution SoftwareDistribution.old

ren %systemroot%\System32\catroot2 Catroot2.old

5. Finally, restart the update services by running the command below, then restart the computer.

net start wuauserv

net start bits

net start appidsvc

net start cryptsvc

3. Fix Image and System File Corruption

File corruption is a common cause of update errors: your device is missing important security and quality fixes. On Windows 11, you may use the DISM and SFC scans to fix said corruption. These scans will replace or repair any corrupted files.

1. Click the magnifying lens on the Taskbar, type cmd, and hit Run as Administrator.

2. Run the two DISM commands below to scan for image corruption and fix any discovered corruption.

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

3. Fix system file corruption by running the SFC scan below.

sfc /scannow

4. Delete the Windows Update Registry Log

You may suspect log corruption if you are still experiencing the update error after all the solutions above. In that case, you should consider deleting the Windows Update registry log. Follow the steps below.

1. Click the magnifying lens on the Taskbar, type cmd, and hit Run as Administrator.

2. Type the commands below, and hit Enter after each one.

Reg delete HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate

Net stop wuauserv >NUL

Cd C:\windows

rmdir softwaredistribution /s /q

Net start wuauserv >NUL

3. Lastly, restart your computer and retry the update to see if the error: your device is missing important security and quality fixes is resolved.

Successfully Updating Windows

The solutions in this guide will help you successfully update your computer without the error: your device is missing important security and quality fixes.

You may reset the computer as a last resort; however, the solutions we offer should suffice in most cases.

Were you able to resolve the error? Please tell us what worked in the comment section below.

FAQs

The post Your Device Is Missing Important Security and Quality Fixes: Fixed appeared first on Next of Windows.

Vous avez un doute, est-ce que Windows 10 est bien à jour. Est-ce que la dernière version de Windows 10 est installée ?

Pas de panique. Ce tutoriel vous apprend les différentes façons de vérifier si Windows 10 est à jour.

Comment vérifier si Windows 10 est à jour

Vérifier si des mises à jour sont en attente

Dans Windows 10, les mises à jour s’installent automatiquement par Windows Update.
Ce dernier est un client qui tourne en permanence sur Windows 10 et vérifie régulièrement si des mises à jour sont disponibles.

Vous pouvez vérifier dans Windows Update si des mises à jour sont disponibles :

• Faites un clic droit sur le menu Démarrer puis Paramètres
• Ensuite, accédez à Mise à jour et sécurité

• Lorsque toutes les mises à jour sont installées, un message indique : “Vous êtes à jour“
• Un bouton Rechercher les mises à jour permet de lancer une nouvelle vérification

Enfin la page suivante de Microsoft donne des informations sur l’historique des mise à jour : Historique des mises à jour de Windows 10

La dernière version est Windows 10 22H2

Depuis la sortie de Windows 10, plusieurs versions ont été publiées à travers des mises à jour de fonctionnalités.
Aujourd’hui, la dernière version est Windows 10 22H2. Aucune nouvelle version ne sera publiée.
Vous pouvez vérifier si cette version est installée et si votre système est à jour.
Voici comment faire :

• Sur votre clavier, appuyez sur la touche + R
• Dans la fenêtre exécuter, saisissez winver et OK
• Vérifiez que dans la fenêtre “A propos de Windows“, vous avez bien version 22H2. Si ce n’est pas le cas alors la dernière version de Windows 10 n’est pas installée

• Pour installer la dernière version, suivez ce guide :

Voici l’historique des versions de Windows 10 :

Version	Version OS	Date	Liens / Commentaires
22H2	19045	Octobre 2022	Comment télécharger et installer Windows 10 22H2
21H2	19044	Octobre 2021	Windows 10 21H2 : les nouveautés
21H1	19043	Mai 2021	Windows 10 21H1 (2104) : les nouveautés
20H2	19042	Octobre 2020	Windows 10 20H2 : les nouveautés
2004	Redstone 8, 19041	Mai 2020	Windows 10 2004 : les nouveautés
1909	Redstone 7, Build 18363 - 19H2	Septembre 2019	Les nouveautés de Windows 10 1909
1903	Redstone 6, Build 18362 - 19H1	Mai 2019	Les nouveautés de Windows 10 1903
1809	Redstone 5, build 17763	Novembre 2018	Nouveautés dans Windows 10 1809
1803	Redstone 4, build 17134	Avril 2018	Nouveautés dans Windows 10 1803
1709	Redstone 3, build 16299	Octobre 2017	Nouveautés de Windows 10 1709 (Fall Creators Update)
1703	Redstone 2, build	Avril 2017	Nouveautés de Windows 10 1703 (Creators Update)
1607	Redstone 1, build 14393	Août 2016	Mise à jour Windows 10 anniversaire (1607)
1511	Threshold 2, build 10586	10 Novembre 2017

L’article Savoir si Windows 10 est à jour et à la dernière version est apparu en premier sur malekal.com.

Updating your Windows computer is critical to optimal performance. However, the update process may encounter some challenges. Recently, we have heard people talk of the 0x8000ffff Windows 11 update error.

This error may indicate software conflicts, corrupted files, or problems with essential update components. Let us run you through some of the most effective fixes in this guide.

1. Run the Windows Update Troubleshooter

Windows has some built-in troubleshooters. The Windows update troubleshooter is one of them. This tool will scan your computer for updates and fix problems or recommend corrective actions. Follow the steps below to run the utility.

1. Press Windows + I to open the Settings app.

2. Click the System tab on the left, then click Troubleshoot on the right.

3. Click Other troubleshooters.

4. Click the Run button for Windows Update.

5. Follow the Wizard to complete the process.

2. Run the DISM and SFC Scans

Corrupted installation and system files commonly cause the 0x8000ffff Windows 11 update error. This is because the update process may rely on some of these files to complete successfully. Luckily, on Windows 11, you may employ the DISM and SFC tools to fix said corruption.

1. Press Windows + R to open the Run dialog.

2. Type cmd and hit Ctrl + Shift + Enter.

3. Type the command below, hitting Enter after each one to run the DISM scan.

DISM /ONLINE /CLEANUP-IMAGE /SCANHEALTH
DISM /ONLINE /CLEANUP-IMAGE /CHECKHEALTH
DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH

3. Type the command below and hit Enter to run the SFC scan.

sfc /scannow

3. Perform the Update from the Windows Update Catalog

When updates are not completed successfully, there are chances that certain update components are not working correctly. If this is the case, you may perform a manual update. You will need to download the needed update from the Windows Update catalog. Also, you will need to find the problematic update. Follow the steps below.

1. Press Windows + I to open the Settings app.

2. Click Windows Update on the left pane and Update History on the right.

3. You should see the name of your most recent update. It usually starts with a K. Note the name.

4. head to the Windows Update Catalog website.

5. Past your update in the search bar, click Search, then click Download for the specific update you need.

6. Double-click the download to install it.

4. Reset your Windows Store Cache

Resetting the Store cache will fix corrupted or outdated cache data and conflicting cache entries that may trigger the update error. It also eliminates synchronization and permission issues,

1. Press Windows + R to open the Run dialog.

2. Type the command below and hit Enter.

WSReset.exe

5. Temporarily Disable the .Net Framework Feature

Disabling the.NET framework is one of the best ways to fix the Windows 11 update error with code 0x8000ffff. This is due to the possibility that the component will disrupt the updating process.

1. Press Windows + R, type apwiz.cpl, and hit Enter.

2. Click Turn Windows features on or off.

3. Uncheck all .Net Framework checkboxes and click the OK button.

4. Retry the update and re-enable the .Net framework when the update is complete.

No More Update Error 0x8000ffff

That is all you need to know about the Windows 11 0x8000ffff update error. In most cases, it is an easy fix. In rare situations, you may consider a reinstallation of the operating system. But this is a drastic measure and should be reserved as a last resort.

Do you have questions about the update error? We love to hear them in the comment section below. You may consider similar fixes for the 0x800f0831 Windows Update error.

The post How to Fix Windows 11 Update Error 0x8000ffff appeared first on Next of Windows.

Updating your computer is essential housekeeping to ensure optimal device performance. However, hiccups like the Windows 11 update error 0x800f0831 make it impossible for the process to complete properly.

In the past, we have explored other update errors, but this 0x800f0831 error is mainly associated with the missing manifest of an update package. You should run through the solutions below to fix it.

1. Run the Windows Update Troubleshooter

This is a perfect starting point for the 0x800f0831 Windows 11 update error. The Windows Update installer will scan your computer for update problems, fix them, or recommend solutions.

1. Press Windows + I to open the Settings app.

2. Click the System tab on the left, then click Troubleshoot on the right.

3. Click Other troubleshooters.

4. Click the Run button for Windows Update.

5. Follow the Wizard to complete the process.

2. Reset Windows Update Components

Update components include a group of services, files, and tools that are essential to successfully updating the computer. When some of these components are corrupted, you may reset them to fix the Windows 11 update error 0x800f0831. Follow the steps below.

1. Press Windows + R to open the Run dialog.

2. Type cmd and hit Ctrl + Shift + enter.

3. Type the command below, hitting enter after each one to stop updating components.

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

4. Rename update folders by typing the commands below and hitting Enter after each one.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old

5. Restart the update components by typing the commands below and hitting Enter.

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

3. Manually Fix Partially Installed Components

If a specific update causes the Windows 11 update error 0x800f0831, you may manually download it from the Windows catalog website and install it manually.

1. Press Windows + I to open the Settings app.

2. Click Windows Update on the left pane and Update History on the right.

3. You should see the name of your most recent update. It usually starts with a K. Note the name.

4. head to the Windows Update Catalog website.

5. Past your update in the search bar, click Search, then click Download for the specific update you need.

6. Double-click the download to install it.

4. Run the DISM and SFC Scans

You may use DISM and SFC to fix corruption issues that trigger the Windows 11 update error 0x800f0831 on Windows. These utilities will scan images and system files for corruption and repair or replace any observed corruption.

1. Press Windows + R to open the Run dialog.

2. Type cmd and hit Ctrl + Shift + enter.

3. Type the command below, hitting Enter after each one to run the DISM scan.

DISM /ONLINE /CLEANUP-IMAGE /SCANHEALTH
DISM /ONLINE /CLEANUP-IMAGE /CHECKHEALTH
DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH

3. Type the command below and hit Enter to run the SFC scan.

sfc /scannow

5. Perform an In-place Upgrade

An in-place upgrade should be your last resort because this solution may lead to some data loss. However, it is very effective. You must visit the Windows 11 ISO download website and follow the steps below.

1. Click the Download Now button to get the ISO image.

2. Double-click the downloaded file to run it.

3. When you get to the Install Windows 11 screen, ensure that you uncheck I want to help make the installation of Windows better, then select the Change how Windows Setup download updates option.

4. Click Not right now on the subsequent window, then click Next.

5. Accept the user terms.

6. Click Choose what to keep on the Ready to install window, then select what you like to preserve.

7. Finally, click Install.

Update Windows 11 Without Hitch

Now, you can update your Windows 11 without the 0x800f0831 update error. While we have offered some effective solutions, you should start with the most appropriate ones.

Let us know what worked in the comment section below.

FAQ

The post Windows 11 Update Error 0x800f0831 appeared first on Next of Windows.

Avez-vous rencontré le code d’erreur 0x8007010b en essayant de mettre à jour Windows 10 ou Windows 11 vers la dernière version ? Eh bien, cette erreur survient généralement en raison de répertoires invalides, de fichiers système corrompus, d’images Windows endommagées, etc. Ce bogue est souvent accompagné d’un message d’erreur qui se lit – ERROR_DIRECTORY.

Cela signifie que le dossier contenant les fichiers de mise à jour importants est devenu invalide. Ou bien, l’ensemble du mécanisme de mise à jour a été corrompu. Comme le dossier n’existe pas ou que son nom n’est pas valide, les services de mise à jour ont beau tenter de télécharger les correctifs, ils génèrent toujours une erreur.

Voici plusieurs solutions à appliquer pour corriger l’erreur de mise à jour 0x8007010b dans Windows 10/11.

Comment réparer l’erreur de mise à jour 0x8007010b dans Windows 10/11

Utiliser l’utilitaire de résolution des problèmes de Windows Update

Windows comprend un certain nombre d’outils de dépannage automatisés pour résoudre les problèmes courants.
Il est capable de réinitialiser les composants Windows Update afin de le réparer.
Voici comment utiliser l’utilitaire de résolution des problèmes Windows Update qui résout la plupart des codes erreurs 0X80070057, 0x80070570, 80004005, 0x80073701, 8024a000, ox8024001e, 0x800700d8, …

• Sur votre clavier, appuyez sur les touches + R
• Puis msdt.exe -id WindowsUpdateDiagnostic

• Dans la liste, cherchez Windows Update puis cliquez dessus
• Cliquez sur Exécuter l’utilitaire de résolution des problèmes

• L’outil de dépannage démarre et analyse Windows 10 pour détecter les problèmes et les résoudre

• Laissez vous guider. Un redémarrage de du PC est alors nécessaire pour prendre en compte les changements

• Enfin relancez une recherche de mise à jour afin de vérifier si Windows Update est réparé, fonctionne correctement et si les codes erreurs ou autres problèmes sont résolus

Réparer les fichiers systèmes manquants ou endommagés

Si l’erreur 0x8007010b persiste même après avoir recherché les bogues et les erreurs, il se peut que des fichiers système soient corrompus ou manquants sur l’ordinateur. Pour réparer ces fichiers, Windows propose un excellent programme intégré – l’utilitaire SFC. Voici comment utiliser cet outil.

Pour réparer les fichiers systèmes de Windows 10 ou Windows 11, on utilise les utilitaires SFC (vérificateur de fichiers systèmes) et DISM.
Ces deux outils s’utilisent en invite de commandes.

• Ouvrez une invite de commandes :
  • Comment ouvrir une invite de commandes sur Windows 10
  • Comment ouvrir Windows Terminal sur Windows 11
• Puis pour faire une vérification et réparation SFC, saisissez :

sfc /scannow

Laisse le vérificateur de fichiers systèmes analyser Windows 10 ou Windows 11.
Enfin si des fichiers systèmes sont corrompus, SFC tente de les réparer.

Ensuite on peut utiliser DISM pour réparer les images de Windows 10/11.
Toujours depuis l’invite de commandes, saisissez successivement les commandes suivantes :

Dism /Online /Cleanup-Image /CheckHealth

Plus de détails dans l’article suivant :

Réinitialiser composants Windows Update

La mise à jour de Windows se compose de plusieurs éléments et chacun d’entre eux doit fonctionner correctement et efficacement. Si l’un de ces composants est corrompu, cela peut entraîner différents bogues ou erreurs liés à la mise à jour. Les principaux composants sont les suivants : services cryptographiques, transfert intelligent en arrière-plan, service d’identification des applications et service de mise à jour de Windows. Ainsi, pour résoudre l’erreur 0x8007010b, vous devez réinitialiser tous ses composants en suivant les étapes ci-dessous.

• Ouvrez une invite de commandes en administrateur
• Puis copiez/collez le contenu suivant :

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

• Redémarrez le PC afin de prendre en compte les changements
• Puis relancez les mises à jour Windows Update

Un article existe sur le site dédié avec d’autres méthodes pour vider le catalogue Windows Update et résoudre les erreurs d’installation :

Installer la mise à jour manuellement

Souvent, les erreurs de mise à jour résultent simplement de l’installation incorrecte de correctifs de sécurité récents. Si vous avez récemment installé une mise à jour cumulative, il vous suffit de ramener le système d’exploitation à son état précédent.

Si ce n’est pas le cas, vous devez télécharger et installer manuellement le dernier paquet autonome sur l’ordinateur. Pour ce faire, vous devez connaître le numéro “KB” des mises à jour en attente en suivant les étapes ci-dessous.

Afficher l’historique des mises à jour pour récupérer le numéro de la mise à jour en erreur :

• Appuyez simultanément sur + I pour ouvrir l’interface utilisateur des paramètres
  • Sur Windows 10, cliquez sur Mise à jour et sécurité
  • Sur Windows 11, allez dans Windows Update
• Dirigez-vous vers le volet de droite et cliquez sur “Afficher l’historique des mises à jour“
• Sur l’écran suivant, vous pouvez trouver la liste des mises à jour qui ont échoué.
• Notez le numéro de mise à jour KBXXXX et suivez la partie suivante

Plus de détails : Comment afficher l’historique de mise à jour Windows Update

Une fois le numéro KBXXXX de la mise à jour en échec d’installation identifié, vous pouvez l’installer manuellement :

• Visitez le site web Microsoft Update Catalog et tapez le numéro “KB” mentionné ci-dessus
• Une liste de résultats concordants s’affiche, choisissez-en un en fonction de l’architecture du système
• Cliquez sur Télécharger à côté du lien de mise à jour, puis sur le lien supérieur de la fenêtre qui s’affiche
• Lorsque le téléchargement est terminé, cliquez deux fois sur le fichier d’installation pour mettre à jour le système d’exploitation

Plus de d’aide : Télécharger et installer des mises à jour de Windows manuellement

Windows Repair

Windows Repair est un utilitaire gratuit qui permet de réparer des composants et fonctionnalités de Windows.

• Téléchargez Windows Repair puis installez le

• Windows Repair se lance automatique, acceptez les conditions d’utilisation

• Toutefois, il est conseillé de faire les réparations en mode sans échec. Pour cela, en bas, cliquez sur Reboot To Safe Mode.. ou suivez ce guide complet : Redémarrez Windows en mode sans échec

• Puis relancez Windows Repair
• Cliquez sur l’onglet Réparation – Principal
• La liste des type de réparation de Windows s’affiche : cliquez sur Préréglages : Réparations communes

• Vous obtenez alors la liste ci-dessous, laissez les éléments cochés

• Enfin cliquez en bas à droite sur Démarrer les réparations
• L’opération se lance avec une succession d’étape… des fenêtres noires peuvent s’ouvrir ou se refermer

• Laissez terminer, un message vous indique que la réparation Windows Repair est terminée
• Redémarrez le PC en mode normal de Windows

Plus de détails dans ce tutoriel complet :

Réparer Windows 10 ou Windows 11

Lorsque Windows est totalement endommagé et que les problèmes sont trop nombreux, vous pouvez tenter de réparer Windows 10, 11 sans perte de données et en conservant les programmes installés.
Cela permet de rétablir un système fonctionnel à partir des fichiers ISO et images de Windows.
La procédure est décrite pas à pas dans cet article :

• Comment réparer Windows 10 sans perte de données
• Comment réparer Windows 11 sans perte de données

Il s’agit d’une opération de réinitialisation et de remise à zéro qui supprime les applications et remet le système à son état d’origine.
C’est la solution radicale pour retrouver un système fonctionnel :

• Comment réinitialiser Windows 10
• Comment réinitialiser Windows 11

L’article Réparer l’erreur de mise à jour 0x8007010b dans Windows 10/11 est apparu en premier sur malekal.com.

This guide will examine the Modules Installer Worker high CPU usage. Showing you some common causes and how to fix it in some easy steps.

Computer users fear high CPU usage because it may lead to slow performance, overheating, reduced battery life, instability, and crashes. The steps below will help avoid these negative consequences.

What is Windows Modules Installer Worker?

On Windows 11, the WMIW, TiWorker.exe, or Windows Modules Installer Worker is an important background process that handles several essential system updates and maintenance tasks. Its functions include checking and installing updates and managing system files.

When you experience the Windows Modules Installer Worker high CPU usage it may be because of the following:

• Active updates and installations
• Corrupted or stuck updates
• Background maintenance tasks
• System file corruption

You should be able to resolve it with the solutions below.

How to Fix Modules Installer Worker High CPU Usage

1. Set Windows Update to Manual

You can control when updates are made by setting the Windows Update service to manual. This means rather than have updates when other resource-intensive programs are running; you run updates only when the computer is idle.

1. Click the magnifying lens on the taskbar, type services, and click the Services app.

2. Scroll down, then double-click Windows update.

3. Set Startup type to Manual, then click Apply and OK.

2. Repair Corrupted System Files

Corrupted system files commonly cause the Modules Installer Worker high CPU usage. This is because they affect the update process and may sometimes cause it to get stuck and take longer than normal. You may run the SFC scan to fix the file corruption.

1. Press Windows + R to open the Run dialog.

2. Type cmd and hit Enter to launch an elevated Command Prompt.

3. Type the command below and hit enter to launch the SFC scan.

sfc /scannow

4. Restart your computer.

3. Run the Windows Update Troubleshooter

Windows 11 comes with built-in troubleshooters. The Windows Update troubleshooter is one of them. This tool will scan your computer for update problems and fix them.

1. Press Windows + I to launch the Settings application.

2. Click the System tab on the left, then click Troubleshoot on the right.

3. Click Other troubleshooters.

4. Click the Run button for Windows update, and follow the wizard to complete the process.

4. Delete Your SoftwareDistribution Folder

Files required for Windows updates are temporarily stored in the SoftwareDistribution folder. Occasionally, the SoftwareDistribution files clash with the latest updates, leading to a high CPU utilization of the Windows Module Installer Worker. Note that this process deletes your update history.

1. Click the magnifying lens on the taskbar, type services, and click the Services app.

2. Right-click on Windows update and click Stop.

3. Press Windows + E to open File Explorer.

4. Navigate to the path below:

C:\Windows

5. Scroll down to SoftwareDistribution, click the folder, and click the Delete icon.

5. Stop the TiWorker.exe Process

It’s usually advisable to close TiWorker.exe and relaunch it. You may also search for additional apps, vying for precious computer resources with Windows Modules Installer Worker or TiWorker.exe. For instance, svchost.exe also results in excessive CPU utilization; if you can fix it, TiWorker.exe will have more resources.

1. Press Ctrl + Shift + Esc to open the Task Manager.

2. Click the Details tab on the right pane, right-click TiWorker.exe, and click End task.

No More Performance Lags and Crashes

The Modules Installer Worker high CPU usage problem will cause tremendous performance lag. However, these solutions are often very easy, and with a few clicks, the problem will be a thing of the past.

Let us know if you have successfully fixed it in the comments below.

FAQ

The post Fixed: Modules Installer Worker High CPU Usage appeared first on Next of Windows.

Windows updates are essential for the proper functioning of your computer. They often come with bug fixes and security patches, ensuring your computer performs optimally. However, you may encounter a few problems during the process, like the 0x8024ce16 Windows update error.

If you have faced this error, in this article, we walk you through the most effective steps for fixing it. Let us get started.

What Are the Causes of the 0x8024ce16 Windows Update Error?

The main reasons you encounter this problem are the following:

1. Corrupted Windows Update files.
2. Windows Update database issues.
3. Software bugs and conflicts.

Any of the solutions above should effectively fix it.

How do I Fix the 0x8024ce16 Windows Update Error?

1. Run the Windows Update Troubleshooter

Windows 11 comes with some built-in troubleshooters. The Windows update troubleshooter is one of them. This program will scan the device for updated problems and fix them or recommend the best solutions.

1. Press Windows + I to open the Settings app.

2. Click the System tab on the left pane, then click Troubleshoot on the right.

3. Click Other troubleshooters.

4. Click the Run button for Windows Update, then follow the wizard to complete the process.

2. Run the DISM and SFC Scans to Fix File Corruption

When Windows installation or system file corruption triggers the 0x8024ce16 Windows update error, you may use the built-in DISM and SFC scans to fix the problem. Simply follow the steps below.

1. Launch the Run dialog by pressing Windows + R.

2. Type cmd and hit Ctrl + Shift + Enter to open an elevated Command prompt.

3. Type the command below and hit Enter to scan for Image errors.

DISM /Online /Cleanup-Image /ScanHealth

4. Type the command below and hit Enter to fix all discovered image errors.

DISM /Online /Cleanup-Image /RestoreHealth

5. Rund the command below to fix corrupted system files on the computer.

sfc /scannow

3. Clean the Windows Update Temporary Cache Folder

By cleaning the Windows update temporary folder, you will remove corrupted update data that triggers the 0x8024ce16 Windows update error.

1. Click the magnifying lens on the taskbar, type services, and click the Services app.

2. Right-click Windows update and click Stop.

3. Press Windows + R, enter the path below and hit Enter.

%windir%\SoftwareDistribution\DataStore

4. Delete all Folders in this path, then reopen the service, right-click Windows Update, and click Start.

4. Reset Windows Update Components

Due to problems with the Windows Update service and database, you may encounter the 0x8024ce16 Windows update error. Resetting the update components will remove corrupted files and reset the Windows Update service and database.

1. Press Windows + R to Launch the run dialog.

2. Type cmd, then hit Ctrl + Shift + Enter to launch an elevated Command Prompt.

3. Type the scripts below, hitting enter after each to stop essential update services.

net stop wuauserv
net stop cryptsvc
net stop bits
net stop msiserver

4. Type the scripts below, hitting enter after each to rename update folders.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

5. Restart the update services by running the scripts below.

net start wuauserv
net start cryptsvc
net start bits
net start msiserver

5. Run System Restore

As a last resort, you may run the system update utility. This utility will ensure that the computer is reverted to a state when it worked properly without the update error. To use the Restore utility, you must have created a restore point. However, this fix may work if there is an automatically created restore point as well.

1. Type restore on Windows Search and select the Recovery option.

2. Click the Open System Restore option on the Control Panel.

3. Select Choose a different restore point and click the Next button.

4. Select a different restore point from the available options and click Next.

5. Lastly, click the Finish button. The process will begin, and your computer may restart as the restore runs.

Recovering From the 0x8024ce16 Windows Update Error

Update errors are not uncommon to Windows users and, in most cases, pretty easy to fix. In this guide, we have worked you through easy solutions in no particular order. It would be best if you stuck to whichever feels the most practical.

Please tell us how effective they have been in the comment section below.

The post 0x8024ce16 Windows Update Error: FIXED appeared first on Next of Windows.

Windows Update MiniTool est une application portable capable de remplacer Windows Update de Windows. Ce dernier est intégré aux systèmes d’exploitation Windows et gère les mises à jour en recherchant régulièrement la présence de mises à jour disponibles avant de les installer automatiquement.

Malheureusement, l’outil Windows Update fournit par défaut dans les différentes versions de Windows (Windows, 7, Windows 10, Windows 11, etc.), présente son lot d’inconvénients :

• ☞ L’utilisateur n’a pas vraiment la main sur l’installation des mises à jour.
• ☞ Certaines mises à jour sont difficiles, voire impossible à bloquer.
• ☞ La bande passante de votre connexion internet peut vite être saturée.

Pour remédier à cela, il peut être intéressant de se tourner vers à une autre application. Ici, nous vous présentons la dernière version disponible depuis 2022 du logiciel pour Windows Update gratuit : Windows Update MiniTool. Dans ce tutoriel, nous vous expliquons ce que c’est et comment utiliser cet outil presque magique !

Qu’est-ce que Windows Update MiniTool ?

Windows Update MiniTool est une alternative à la fonctionnalité standard Windows Update (WU) intégrée dans Windows 10 et Windows 11. Il s’agit d’une application client gratuite sortie en 2015 et créée par stupide user de forum.ru-board.com, un programmeur installé en Russie. Cet outil est parfois comparé au module externe PowerShell « PSWindowsUpdate », mais en plus avancé et convivial. Windows Update MiniTool propose bien plus de fonctionnalités que le service intégré WU, dont :

• La recherche de mises à jour pour Windows.
• Le téléchargement des mises à jour sélectionnées que vous souhaitez installer.
• L’installation des mises à jour.
• La suppression des mises à jour installées si celles-ci rencontrent des problèmes ou ne sont pas compatibles avec des logiciels ou des périphériques que vous utilisez.
• Le masquage des mises à jour indésirables afin de ne pas les revoir lors d’autres recherches de mises à jour.
• L’obtention de liens directs vers les fichiers de mise à jour au formats .cab, .exe ou .psf.
• La visualisation de l’historique des mises à jour afin de vérifier rapidement les mises à jour effectuées dans le temps.
• La configuration des mises à jour automatiques selon vos préférences.

Notez cependant que Windows Update MiniTool ne se substitue pas entièrement à Windows Update, car il utilise l’infrastructure de mise à jour de Windows et tous les téléchargements se font au travers de WU. Ce n’est donc pas un gestionnaire de téléchargement indépendant.

Présentation de Windows Update MiniTool

Ci-dessous, une capture d’écran de l’interface de Windows Update MiniTool dans sa dernière version (22.04.2022) à ce jour. Nous vous proposons de faire  un tour du propriétaire avant de passer au cœur du sujet, à savoir l’utilisation de Windows Update MiniTool.

1. Ici, s’affichent les quantités de mises à jour disponibles, installées et cachées, ainsi que l’historique des mises à jour effectuées jusqu’à présent (devient réellement actif après la synchronisation avec Windows Update).
2. Dans cet encart, apparaissent les différentes mises à jours. Lorsque c’est vide c’est qu’il n’y a aucune nouvelle mise à jour disponible pour le moment.
3. Ces boutons servent à :
   • synchroniser et vérifier les mises à jour ;
   • télécharger les mises à jour ;
   • installer les mises à jour ;
   • désinstaller les mises à jour ;
   • cacher une mise à jour.
4. Vous modifiez ici les paramètres de recherche, à commencer par choisir une connexion à Windows Update, Windows Store ou DCat Flighting Prod. Puis, vous pouvez opter pour Microsoft Update, inclure les MàJ remplacées, inclure les pilotes et activer le mode hors-ligne.
5. Vous pouvez aussi configurer la mise à jour automatique :
   • non configurée ;
   • désactivée ;
   • mode notification ;
   • télécharger seulement ;
   • autre.

Windows Update MiniTool : gérer les mises à jour de Windows

Voici la procédure pour pouvoir télécharger Windows Update MiniTool, l’installer et effectuer les réglages nécessaires.

Télécharger Windows Update Minitool 2022

1.  Télécharger la dernière version de Windows Update Minitool et décompressez l’archive ZIP téléchargée.
2. Lancez l’exécutable correspondant à la version de votre système : wumt_x64.exe pour les systèmes 64 bits et wumt_x86.exe pour les systèmes 32 bits. Cliquez ici pour savoir comment trouver la version de votre système.
   
3. L’application se lance.
   

Synchroniser avec Windows Update et vérifier les mises à jour

1. Commencez par vérifier les mises à jour grâce à la synchronisation avec Windows Update. Cliquez sur le bouton représentant la double-flèche.
   
   La synchronisation prendra quelques secondes.
2. La liste des mises à jour disponibles apparaît au centre de la fenêtre. Elles sont en attente de téléchargement.
   

Télécharger les mises à jour

Les mises à jour affichées dans la liste après synchronisation sont des mises à jour disponibles pour votre système. Elles ne sont pas encore téléchargées. Vous pouvez choisir de télécharger seulement les mises à jour qui vous intéresse pour les installer plus tard.

1. Cochez la ou les mises jour que vous souhaitez télécharger.
   
2. Cliquez ensuite sur le bouton de téléchargement à gauche.
   
   Les mises à jour sélectionnées sont maintenant téléchargées.

Installer une mise à jour

1.  Veillez à toujours être sur l’onglet Windows Update à gauche.
   
2. Cette fois-ci, nous allons installer une mise à jour. Cochez la ou les mises à jour voulues et cliquez sur le bouton d’installation.
   
3. La mise à jour est maintenant terminée. Vous pouvez remarquer le message de confirmation en bas indiquant : Installation des mises à jour… Succès.
   

Supprimer une mise à jour

1. Si vous souhaitez supprimer une mise à jour, il faut vous rendre cette fois dans l’onglet Installée(s) qui contient la liste de toutes les mises à jour installées.
   
2. Sélectionnez la mise à jour que vous souhaitez supprimer et cliquez sur la corbeille à gauche pour lancer la suppression.
   

Cacher une mise à jour

Vous pouvez également cacher une mise à jour pour l’empêcher de s’installer automatiquement.

1. Dans l’onglet Mise(s) à jour, sélectionnez la mise à jour que vous souhaitez cacher et cliquez sur le bouton Cacher.
   
2. La mise à jour se déplace dans la section Cachée(s). Ces mises à jour ne s’installeront jamais, même manuellement.
   
   i Note : pour débloquer la mise à jour, il vous suffit de la cocher et d’appuyer de nouveau sur le bouton Cacher. La mise à jour repassera dans l’onglet Mise(s) à jour.

Consulter l’historique des mises à jour

Avec Windows Update MiniTool, vous pouvez très facilement (re)trouver toutes les mises à jour installées sur votre ordinateur depuis le début.

Pour cela, cliquez sur Historique des m. à j. Vous pourrez constater qu’il y en a 542 dans mon cas.

L’origine de l’installation est précisé dans la colonne de gauche, où vous pourrez y lire :

• Windows Update MiniTool : mise à jour réalisée par le programme du même nom.
• MoUpdateOrchestrator : mise à jour réalisée par Windows Update.

Configurer les paramètres de recherche

Choisir la base de recherche

Les paramètres de recherche de Windows Update MiniTool permettent d’affiner les recherches de mises à jour. Par défaut, la base de recherche Windows Update est choisie. Voici une brève présentation des bases de recherche :

• DCat Flighting Prod : une source de mise à jour alternative pour des mises à jour spécifiques. Selon Microsoft, à partir de Windows 10 1709, les mises à jour des fonctionnalités sont toujours fournies par le service DCat.
• Windows Store (DCat Prod) : les recherches de mises à jour se limitent seulement au Microsoft Store et les applications issues de celui-ci.
• Windows Update : le service de mises à jour intégré à Windows et utilisé par défaut.

Les options de recherche en détail

Ensuite, vous avez d’autres options possibles pour les recherches de mises à jour :

• Microsoft Update : tandis que WU fournit des mises à jour pour le système d’exploitation et certains logiciels Microsoft intégrés, Microsoft Update offre des mises à jour d’autres produits (Microsoft Office, Visual Studio, SQL Server, etc.).
  i Note : nous vous conseillons fortement de cocher cette option.
• Inclure les m. à j. remplacées : en activant cette option, Windows Update MiniTool affichera toutes les mises à jour disponibles, y compris celles qui ont été techniquement remplacées par des versions plus récentes. Cela peut être utile pour l’archivage, le dépannage ou si vous avez besoin d’installer une mise à jour spécifique pour une raison particulière.
• Inclure les pilotes : cette option est cochée par défaut et permet de rechercher les dernières versions des pilotes de périphériques. Gardez-la active pour la sécurité de votre appareil.
• Mode hors-ligne : ce mode permet de télécharger toutes les mises à jour disponibles dès que votre ordinateur se connecte à Internet. Vous pourrez alors installer les mises à jour quand vous le souhaitez même en étant déconnecter d’Internet (hors-ligne). Cela est très pratique en cas d’utilisation d’un réseau internet peu fiable.

Configurer la mise à jour automatique

Nous détaillons ici les options possibles pour configurer la mise à jour automatique avec Windows Update MiniTool :

• Non configurée : c’est le réglage par défaut. Certaines mises à jour critiques peuvent s’installer automatiquement.
• Désactivée : vous décidez de désactiver la mise à jour automatique. Aucune mise à jour ne démarrera sans votre consentement.
• Mode notification : vous recevez une notification avant l’installation d’une mise à jour.
• Télécharger seulement : les mises à jour sont automatiquement téléchargées, mais pas installées. Ce sera à vous de les installer manuellement.
• Autre : cette option n’est pour l’instant pas utilisable.

Liens utiles

• Windows 10 reporter, différer les mises à jour de Windows Update.
• Windows 10 : désactiver les mises à jour de Windows Update.
• Réparer Windows Update (échec des mises à jour et erreurs).
• Windows 10 : masque/désactiver une mise à jour dans Windows Update.

 

Source