Why is Microsoft providing wrong codebase updates for an Intel based cpu machine running Microsoft Windows Professional 10 and acting like a virus?

Anonymous
2019-04-02T18:27:35+00:00

Microsoft Windows Professional 10 was using a 64 bit intel chip was downloading only AMD64 updates. I am still receiving these in reference to 1809 update and have to reboot into safe mode and remove the contents of the directory every time the delay ticker is met to stop a 16 hour update cycle with a 52% install and the a forced return to the previous version as the update is trying to apply AMD code to my windows installation on an Intel 64bit processor. Does anyone have a hack on this ticker to reset it at startup to zero so the delay stays in force?

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

82 answers

Sort by: Oldest
  1. Anonymous
    2019-05-22T16:27:01+00:00

    Maybe you should run those "mysterious" files through an online scanner like VirusTotal which will run it through many engines (they use 70)?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-05-23T08:24:31+00:00

    With such a cheery attitude that you have when conversing with others, it's no wonder you can't find a solution to your issue.

    Using a little honey will get much better results than a pound of salt.

    Its fairly obvious you are employed in the legal profession and some of us are doing this for nothing.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-05-23T08:39:57+00:00

    Submission Summary


    Files Submitted

    # Filename MD5 Determination Signature Protection Name RR Seq#
    1 wups.dll 26e6588f4644f4f74fcc23108fb454 Clean N/A N/A
    Developer Notes:
    1. wups.dll is a clean file.

    Submission Summary


    Files Submitted

    # Filename MD5 Determination Signature Protection Name RR Seq#
    1 wups2.dll 3ef9ca763b9bb76e6c89d11a5f5160 Clean N/A N/A
    Developer Notes:
    1. wups2.dll is a clean file.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-05-23T08:40:30+00:00

    How can then this not be registered as a new virus . If this is not a virus with a know signature? Then do I have to conclude is is a purposeful action to cause potential harm?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-05-23T09:08:27+00:00

    Maybe you should run those "mysterious" files through an online scanner like VirusTotal which will run it through many engines (they use 70)?

    Symantec has already notified me that this signature is not recognized currently therefore VirusTotal would most likely share same resource of virus definitions.

    Was this answer helpful?

    0 comments No comments