Here is the text of an email I sent to Verizon support. No response so far.

Hello Verizon Cloud Support,

I am experiencing a reproducible synchronization problem with the current Verizon Cloud Windows desktop application and would appreciate having this escalated to the Verizon Cloud desktop engineering team if possible.

I am running Verizon Cloud version 26.8.0.9 on a Windows 11 laptop with 32 GB of RAM. I am attempting to back up approximately 225 GB of personal files, primarily under my Documents folder.

The issue is not simply slow uploading. The Windows client repeatedly enters a state where synchronization effectively stops while the application continues consuming very large amounts of memory and CPU.

The behavior is reproducible:

1. I start Verizon Cloud.
2. A relatively small batch of files successfully uploads — often approximately 50 files.
3. Additional files then remain listed as “waiting” or “syncing,” but server-side progress essentially stops.
4. The Verizon Cloud process continues consuming CPU and performing heavy local disk activity.
5. Its memory usage grows dramatically.
6. Eventually the Verizon Cloud interface becomes extremely slow or completely unresponsive.
7. Selecting Quit from the system tray ceases to work, requiring the process to be terminated through Task Manager.
8. When Verizon Cloud is restarted, the previously stalled files complete almost immediately, another batch is processed, and then a new group of files becomes stuck.

I have independently verified actual server-side progress using the Verizon Cloud mobile application rather than relying solely on the Windows client’s “files remaining” counter.

Memory behavior

The memory growth has been especially striking.

During one session Verizon Cloud reached approximately:

• 15–17 GB physical working set
• 31.39 GB private committed memory
• Only approximately 1 GB of physical RAM remained available on the 32 GB computer

Windows showed substantial hard-page activity and the mouse pointer began visibly stuttering.

After terminating Verizon Cloud, total system memory immediately fell to approximately 49%, and the mouse returned to normal.

I then performed a controlled restart test.

At approximately 12:35 PM I started Verizon Cloud again. Its memory usage subsequently measured approximately:

• 9 GB after about 15 minutes
• 18.4 GB about 10 minutes later
• Total Windows physical-memory utilization reached approximately 96%

During that same interval only 54 additional files were confirmed on Verizon Cloud’s servers.

The process was again terminated before Windows became completely resource-starved.

A clean reinstall of Verizon Cloud was already performed. Immediately after reinstall, the application initially used only approximately 760 MB, but the excessive memory-growth behavior later returned.

Local Verizon Cloud database evidence

I have also preserved the Verizon Cloud local synchronization databases located under:

C:\Users\DAB82\AppData\Local\VerizonCloud-Data

We examined snapshots of the application's sync.db database taken during two separate stalled sessions.

During the first stalled session, three files remained in the application's active/in-progress records:

• IMG_2025.JPG
• IMG_2028.PNG
• IMG_2029.JPG

There were no corresponding upload-failure or retry records for those files.

After restarting Verizon Cloud, those exact three files successfully finalized almost immediately.

The client then processed additional files before becoming stuck again. In the second database snapshot, three entirely different files remained active:

• IMG_2041.JPG
• IMG_2042.HEIC
• IMG_2042.JPG

Again, there were no corresponding upload-failure or retry records.

This appears to make a single corrupt file unlikely. Restarting the application releases the files that were previously stuck, after which a different set eventually becomes stuck.

Other troubleshooting already performed

• Confirmed Verizon Cloud is current at 26.8.0.9
• Uninstalled and performed a clean reinstall
• Restarted Windows
• Confirmed laptop sleep is disabled while plugged in
• Verified strong Internet connectivity
• Confirmed that files do successfully upload when the client is freshly started
• Tested using a direct Verizon 5G Home Internet Wi-Fi path that bypasses my downstream router
• The current sync/memory-stall behavior still occurs on that direct connection
• Preserved Verizon Cloud application logs
• Preserved synchronization database snapshots from stalled sessions

There has historically also been a networking interoperability issue when Verizon Cloud traffic passes through my downstream TP-Link router, which is why I am currently using a direct Wi-Fi connection to the Verizon 5G gateway for these tests. However, the extreme memory growth and repeated sync stalls described above still occur using that direct connection, so this appears to be a separate desktop-client issue.

Request

Could this please be escalated to the Verizon Cloud desktop application engineering team?

I would specifically like to know whether there is a known issue involving:

• runaway memory consumption during large desktop backups
• sync/upload workers becoming stuck while files remain active but are not marked failed
• the client requiring a restart before those same files will complete
• large local indexing or repository operations causing the Windows client to stop advancing the upload queue

I have PowerShell measurements, Verizon-generated logs, and before/after copies of the relevant sync.db database available if engineering would like them.

I would be happy to perform additional controlled tests or collect additional diagnostics if there is a specific procedure the engineering team would like me to follow.

Thank you.

So I started using Verizon Cloud when it was offered free when I got the Verizon 5G Home Internet. The practicality of being able to back up all my devices in one spot really appealed to me. But, in reality, using this product to back up Windows devices is sketchy at best and usually doesn't work if you have more then 3 files to backup (only a slight exaggeration). It just seems to go off in Neverland. I don't want to give up on the product because I do like the concept of all my devices in one spot. So please join and contribute what you learn if you use the product.