Could this be malware?


Recommended Posts

5 hours ago, devnulllore said:

So far no more issues and every time I re-enable the accent color option in desktop colors the issue returns. I will leave it off for a few days before I consider the issue fixed.

You will be back at some point. This is not a typical or known issue and again is video card related. The next driver update or windows update or fart in the wind will trigger this issue again.  You are simply disabling a feature to mask a symptom. 

What I don't get is how is someone changing their background every minute when they think they have issues with a video card? And working on "clean" installs... How does such a setup come to be on a clean install - seeing if there is any issues?  I don't get it... It sure doesn't freaking do that out of the box.

  • Like 2
On 10/11/2019 at 9:34 AM, devnulllore said:

Pretty much and local folder

So wait... you're... you've been setting up the wall paper to check every minute and update the accent colour when we've asked you to do clean installs?

 

Meaning when we've been struggling to help you diagnose this it's your customizations that have actually been at fault?

4 minutes ago, Matthew S. said:

So wait... you're... you've been setting up the wall paper to check every minute and update the accent colour when we've asked you to do clean installs?

 

Meaning when we've been struggling to help you diagnose this it's your customizations that have actually been at fault?

It boggles the mind for sure. 

No, the default wallpaper is the Windows 10 logo and the colour "Default Blue".

 

I'm not actually sure what you're doing, none of this thread is really making much sense. You've told us that you've had it on clean installs without any changing anything. You've said you've been auto enrolled into the insider programme, a whole bunch of other things and now you're saying that these customisation settings are default. Is this just a wind up?

Actually, it IS possible this was enabled by default. If he had customized his settings to change the wallpaper every minute and change the color and was logged in with an MSA, those personalization settings are saved.  Those same settings will be reapplied if you reinstall Windows and during the install setup and login with that same MSA account. In his world, he never set them on the clean install - Microsoft did. 

4 minutes ago, Zag L. said:

Actually, it IS possible this was enabled by default. If he had customized his settings to change the wallpaper every minute and change the color and was logged in with an MSA, those personalization settings are saved.  Those same settings will be reapplied if you reinstall Windows and during the install setup and login with that same MSA account. In his world, he never set them on the clean install - Microsoft did. 

That did occur to me a while back, in fact I asked the OP some time ago but no response. But there's just too much going on which isn't making sense.

6 minutes ago, Zag L. said:

Actually, it IS possible this was enabled by default. If he had customized his settings to change the wallpaper every minute and change the color and was logged in with an MSA, those personalization settings are saved.  Those same settings will be reapplied if you reinstall Windows and during the install setup and login with that same MSA account. In his world, he never set them on the clean install - Microsoft did. 

I have that setting on my laptop, and my other machines logged in the with the msa have never pulled it. So possibly, but I personally doubt it. 

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • In the boot options in the UEFI is set to legacy or CMS? It needs to be set to UEFI if it's not already.
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      466
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!