device not ready

11

According to Microsoft, my device is not ready for 2004. I wonder, why are they blaming it on my device? It’s windows 2004 that is not ready, not the other way around,

Comments (11)

11 responses to “device not ready”

  1. lvthunder

    No it's not. It's probably either a piece of software or a hardware driver that needs to be updated to work with 2004.

    • miamimauler

      In reply to lvthunder:

      How does that explain new devices like SB3, SPX and SP7 not being ready then?


      Tech sites are full of people wondering how their new Surface devices that you assume have up to date drivers are unable to handle the update.


      There is more going on here than MS are telling us. Honestly, W10 updates are seriously beccoming an issue and MS needs to get on top of it.

      • epguy40

        In reply to miamimauler:


        maybe you should read this article from Softpedia news:

        news.softpedia.com/news/why-windows-10-may-2020-update-not-available-on-day-one-is-actually-a-good-thing-530150.shtml


        the last few paragraphs of that article just said it all for me:

        "In other words, there’s no reason to be angry with Microsoft not rolling out a feature update on day one for your device. Sooner or later, the update should become available for everyone and waiting is actually the right way to go, as this is pretty much the only way to make sure you’re not coming across bugs ruining the entire experience.


        The last time Microsoft rushed to release a feature update users ended up with their personal files deleted beyond the point where they could be recovered, so yes, this is undoubtedly the better way to go."


        unlike some of you here, I can simply wait longer for 2004 to be "ready" for my computer, even if I have to wait several weeks or a few months for 2004 to show up thru windows update.

        MS has to fix some of THEIR issues on THEIR end as the current 2004 release has some problems of its own

  2. Daninbusiness

    I have a number of PCs of various ages and builds at home (between work, school, spouse, kids, etc), and I'm surprised that not one of them is eligible for the upgrade yet.


    I'm not terribly worked up about it, though one would think that at least one of them would have the option to install it by now.


    This might be a bigger story if there wasn't more significant news already going on.

  3. madthinus

    Not a single one of my three devices is ready either. One, gives me the Windows 10 2004 is out but your device is not ready. That one is my work computer where windows update is turned off by our IT specialist. Don't believe in updates, they only apply selected security patches. Patches that has not been installed because we all work from home.


    I don't get the message on my home desktop or my Surface Pro 4, but I also don't get the warning.


    Looking at my desktop, it does not have any of the "known issues" listed.

  4. wright_is

    It depends, there are known problems with some hardware, if your device has Thunderbolt, for example, the update is on hold, because the drivers don't work properly and there are issues with unplugging and re-plugging. That said, I pushed it (WSUS) to my work laptop (ThinkPad T480) with Thunderbolt and so far, it hasn't caused any problems, although I haven't undocked it whilst in use, yet.

    The updates often require new drivers or firmware updates, because faults in the previous versions have been surfaced due to changes in Windows behaviour (within the "rules", but different to previous versions - E.g. optimized UI processing) or new versions of specific applications and until those patches are officially made available, there are delays in rolling out the new versions - although manually installing will often not show any problems, if you are lucky.

    Why Microsoft's own kit isn't ready is an enigma and a poor show for Microsoft.

    The other thing is, they will have information from the Insiders, which kit is least likely to cause problems and that will be prioritized first, once those devices (and there might be some seemingly odd choices) have upgraded and not showing any major issues, they might be slow to roll it out to other hardware.

    And as it is partially Insider driven, it isn't surprising that current hardware is under represented, Insiders will also often put it on secondary PCs and not their primary devices, so those older devices have a "better" track record than newer kit.

    • miamimauler

      In reply to wright_is:

      "Why Microsoft's own kit isn't ready is an enigma and a poor show for Microsoft"


      Not only is it a poor show by MS it debunks the fanboy claims of blaming OEM's for not keeping their devices updated.

      If MS themselves can't even have their new devices up to date and ready for updating then the OEM's have no chance.

    • navarac

      In reply to wright_is:

      I've been running 20H1 since last December and there has been no mention of any so called problem with Surface computers. I've had it on a old SB3 OK. Anyway I'll shove Ubuntu 20.04 on it instead.

  5. illuminated

    Bundling UI and driver updates into one monster update is a bad idea. I thought that Microsoft learned that with their windows phone updates.

  6. yuanyasmine

    Hi,

    there may be several reasons, including software incompatible with 2004, hardware without drivers for 2004 or incompatible with 2004 and so on.


    Download the windows update assistant and update your OS. Here's the link: https://support.microsoft.com/en-ca/help/3159635/windows-10-update-assistant

    This worked for me.

Leave a Reply