Windows 8 multiple wallpaper sync issue.

By George P
in Microsoft (Windows)

 Share

Recommended Posts

Grand Master

George P Global Moderator

Posted
  • Global Moderator
Posted

Hey guys, I've got two systems running windows 8, my desktop and a hybrid tablet from Samsung. On my desktop I have over 100 different wallpapers set to cycle through once a day, but the tablet only managed to sync with the first 20 and won't get the others. Any ideas?

Grand Master

Detection

Posted
Posted

Maybe? I dunno, that will be the last resort really.

Yea, tablets are best not filled up with things you shouldn't need in the first place

Could try it as a test, then set the walls to rotate every 10 seconds to see if it goes past 20, if it does, you could report it to MS, could be something they overlooked / easily fixed with an update

Grand Master

George P Global Moderator

Posted
  • Author
  • Global Moderator
Posted

I think the problem might be that the different themes got mixed up, there's the theme I have set on the desktop as always, then on the tablet there's a synced theme that shows up. I'll mess with it a bit more tomorrow but I think if both systems are set to synced theme it probably got stuck in some loop and never made it past the top 20 in the list.

I'll update when I figure it out more.

Grand Master

George P Global Moderator

Posted
  • Author
  • Global Moderator
Posted

Ok, after messing with it more I ran into two issues, for some reason the changes I made on my desktop didn't sync over to the tablet but the changes on the tablet synced over without a problem. I think this has something to do with the order of sign in between systems. That is that because my desktop stays on 24/7 and I'm not signing in and out of it often compared to the tablet that the sync follows whatever the newest change is on the system that has the newest login at the time. Or maybe all the desktop theme changes got out of whack and it just blocked them from the desktop though they kept going through fine on the tablet back to the desktop.

Anyways, what I then tried was to move all 100 wallpapers to the tablet and set them up to cycle like I originally did on the desktop. I had set the desktop to some other temp theme with one wallpaper etc. After I made the change on the tablet I waited for it to sync over to the desktop. Once it did I went in to see the settings and found out that once again only the top 20 images had synced back to the desktop and not all 100. This seems to be the limit set to how much data can be synced over. I decided to stop desktop side theme sync on both but keep the rest. Now I just set each to cycle through all the wallpapers on their own independent of each other.

I didn't expect MS to have some type of limit set on the settings sync size but that's what it looks like. This is minor though, I'm sure I'm in the minority here and most people stick with one or a few wallpapers and not 100+ like I do.

  • 1 month later...
Neowinian

NimbusTLD

Posted
Posted

Hey guys, did either of you get any further on this topic? Windows 8 only syncs the first 20 wallpapers between my machines too.

I have tried manually copying them all into the default wallpaper roaming folder. Windows 8 deletes them except the first 20.

I have tried putting my wallpapers into another folder, and pointing the theme to look there. Windows 8 reverts to the default roaming folder.

The only workaround I have found is to disable personalisation synchronisation, which isn't exactly ideal.

Has anyone else found a way to get around this limitation?

Thanks in advance,

NimbusTLD

This topic is now closed to further replies.
 Share
Go to topic listing

  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By zikalify · Posted

      Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • Microsoft confirms Recycle Bin bug across all versions of Windows

      By snowy owl · Posted

      I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs

      By hellowalkman · Posted

      Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • My favorite file manager for Windows 11 finally gets a long-requested feature

      By Malisk · Posted

      And with SO much better perf than the laggy mess that is Files.
    • The official Funny Pictures thread

      By Steven P. · Posted

  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post

  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!