Desktop: Missing overlay icons in fresh Windows 10

Created on 26 Dec 2018  ·  43Comments  ·  Source: nextcloud/desktop

Hey guys, i have installed the nextcloud client version 2.5.1 on two Windows Machines and cant see any overlay icons in the windows explorer.
I even tried it with a fresh installed Windows 10 Pro x64 Version in a virtual Machine! No icons.
bildschirmfoto von 2018-12-26 22-45-05

Tried a couple of things from this thread: https://help.nextcloud.com/t/missing-sync-icons-in-windows-explorer/6610

But its not working.

The command:
regsvr32.exe “C:\Program Files (x86)\Nextcloud\shellext\OCOverlays_x64.dll”

throws an "file not found" error, but the file is available in this directory.

The registry folder: (HKLM\SOFTWARE\Microsoft\WindowsCurrentVersion\Explorer\ShellIconOverlayIdentifiers) also does not contain any OC Keys:
bildschirmfoto von 2018-12-26 22-29-30

The command
reg delete "HKEY_CLASSES_ROOT\CLSID\{0960F090-F328-48A3-B746-276B1E3C3722}" /f
also throws an key not found error.

Uninstalling Microsoft One Drive and deleting the keys in the above picture didnt bring any help.

Regarding Dependency Walker, there are a lot of dependencys missing?:
bildschirmfoto von 2018-12-26 22-52-04

Any ideas ?

bug feature install and update os Windows

Most helpful comment

@nfp0 @stebo23 @zfernezir @camilasan @unix0r @Valiantiam @svenb1234 @jstdoit @rullzer

I found that @rkohser worked for me. So I first followed @jstdoit by installing VC 2017:

So I followed @rkohser instruction by installing VC 2013:

YAY!! I got my icons and shell back!!! WOOT!! My machine is brand-new windows, didn't have VC 2013.

All 43 comments

I'm also having this issue.

image

I would expect it to look like this, which is working correctly on my work PC with a synced folder I have there called "nextcloud"

image

Checked the dependency of the overlay.dll with https://github.com/lucasg/Dependencies

and it says
MSVCP120.dll
MSVCR120.dll

are missing.
Installing/Updating the visual c++ Microsoft Visual C++ Redistributable für Visual Studio 2017 in x86 and x64 didnt bring any help.

Same issue here. The client installs without any error messages but apparently fails to check whether all DLLs it depends on are actually installed.

For me not only the overlay icons are missing but the whole file manager integration, i.e. there is no nextcloud item in the context menu.

For me not only the overlay icons are missing but the whole file manager integration, i.e. there is no nextcloud item in the context menu.

On the fresh Windows 10 Installation in a virtual machine, the file manager integration (Right Click Context Menu) is also not available.
Either is the Nextcloud Shortcout in the favorites of the Windows Explorer installed.

But on another client computer, the Context Menu is available and Nextcloud is also registered as a shortcut in favorites of the windows explorer. But the overlay icons are missing!

Looking forward for some reaction of the devs.

In fact, the icons appear to be available only if the 2.3.3.1 client has been previously installed. As soon as I have installed the old client and restarted the Windows 10 machine, the icons are displayed. An update to 2.5.1 was possible without the symbols disappearing again.

Just tested it with the older installations for windows, but the icons were still missing for me.
But, installed the owncloud client and the icons appeared also for the nextcloud folder!

Maybe, because the nextcloud client is more or less new, most users are upgrading from the owncloud client to the nextcloud client. And not that many new installations with the nextcloud client are happening directly. So there are not so many users getting this issue with missing icons, because of another installed software (nextcloud/owncloud client) that provides the icons.

Maybe some issues in the installer packaging process for windows?

I'm suffering the same problem too...Thanks for any help.

I can't trigger this on a clean VM. But I do not have a proper windows test setup to verify more in depth.

@camilasan can you have a look? Or @juliushaertl ?

I cannot reproduce this on my running vm either, I'll try to setup a clean one.

Hi! Did you reboot the machine after installing/updating the desktop client?

@camilasan Of course

just install Microsoft Visual C++ Redistributable saved me.

@jstdoit What exact version did you install?

On my VM these versions were installed:
Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30501
Microsoft Visual C++ 2017 Redistributable (x64) - 14.14.26406

Just removed them, installed nextcloud-desktop-client.2.5.1 version and got
Microsoft Visual C++ 2017 Redistributable (x64) - 14.14.26406.
But no icons.
Updated to
Microsoft Visual C++ 2017 Redistributable (x64) - 14.16.27027
and still no icons after reboot.

Also tried it with Microsoft Visual C++ 2015 Redistributable (x64) - 14.0.23026, but still nothing happend.

I forgot the version, after add the VC++ support, then run these commands in cmd.exe:

regsvr32 "C:\Program Files (x86)\NextCloud\shellext\OCOverlays_x64.dll"
taskkill /f /im explorer.exe
start explorer.exe

remember to replace the exact OCOverlays_x64.dll's path for your own installation directory

Just have a try.

Well, just installed
Microsoft Visual C++ 2017 Redistributable (x64) - 14.16.27027 and
Microsoft Visual C++ 2017 Redistributable (x86) - 14.16.27027.

Trying to register the dll fails with:
bildschirmfoto von 2019-03-06 13-01-17

I'm running a x64 version of windows.

Edit:
But i managed to register the OCOverlays_x64.dll from the owncloud installation and that worked. The icons are shown and everything is fine.
There are also some differences in the size of the dll files:
The nextcloud OCOverlays_x64.dll 171kB
The owncloud OCOverlays_x64.dll 1765 kB

congrats! maybe the nextcloud's win installation package should notify user to install Microsoft Visual C++ Redistributable though. @unix0r

@jstdoit the thing is, our installer is supposed to install it for you, it is embedded in it. Clearly, I will have to review that...

I also have this issue.
Even on a clean VM, the icons and context menus don't show up.

Running regsvr32.exe “C:\Program Files (x86)\Nextcloud\shellext\OCOverlays_x64.dll” yields the error bellow even though the file is present in the folder.

image

I've reinstalled the Nextcloud desktop app and after rebooting Windows, the icons and menus are back!

I am using a Windows 10 Pro 64bit and I am missing the icons, too. I did a fresh install of the Client (Version 2.5.1final (build 20181204).) several times and several reboots, but it did not help.

Solved: Windows 10, fresh install, Nexcloud client 2.5.2, icons and context menu missing
Instaled ownCloud-2.5.4.11654.11466 client on the same machine. Restart. Did not start ownCloud client, but icons & context menu for Nextcloud appear.

I had the same issue. Installing vcredist 2013 solved it, and enabled to properly register the shell extensions. I can see the icons now.
vcredist 2013 can coexist with 2017.

@nfp0 @stebo23 @zfernezir @camilasan @unix0r @Valiantiam @svenb1234 @jstdoit @rullzer

I found that @rkohser worked for me. So I first followed @jstdoit by installing VC 2017:

So I followed @rkohser instruction by installing VC 2013:

YAY!! I got my icons and shell back!!! WOOT!! My machine is brand-new windows, didn't have VC 2013.

I just followed the track started by @unix0r, writing that MSVCP120.dll was missing.
VS2013 was supplying MSVC 12.0 compiler, so i tried its redist package.
Happy that it worked out for you.

I hope everyone can also check out my new Wikipedia page on Shell Overlay Icons.

https://en.wikipedia.org/wiki/List_of_Shell_Icon_Overlay_Identifiers

There is only 15 overlay icons (4 are reserved by Windows), so effectively 11 overlay icon spaces. I made a list for everyone so they can choose which ones are most important to them.

Windows handles only the first 15 overlay extension entrys. If the Registration in an admin prompt with
regsvr32.exe “C:\Program Files (x86)\Nextcloud\shellext\OCOverlays_x64.dll”
was successful and the Icons does not appear after an restart of Explorer.exe, consider that you have more than 15 Icons registered.

You Fan find an how to in this blog post

@tux1337 Windows OS itself reserves 4 icon overlays, so effectively it's 11 overlay icons available for other programs. (15-4=11). Source

this is somehow crazy... :dizzy_face:
on a Win10x64 Pro testing VM (which never got in touch with dropbox or any other cloud-/sync-software) i installed the nextcloud-client 2.5.2.5231 (via chocolatey.org) and neither the overlay icons nor the context menu were there. :disappointed: exacly as @svenb1234 described at https://github.com/nextcloud/desktop/issues/978#issuecomment-452582418.

  1. installing a bunch of different Visual C++ Redistributable packages didn't change anything.
    EDIT: it seems that installing Visual C++ 2013 Redistributable before the nextcloud-client (or reinstalling it afterwards) does the trick.
  2. after registering the dll manually, described at https://github.com/nextcloud/desktop/issues/978#issuecomment-470078088, at least the overlay icons showed up.
  3. but then after installing owncloud-client 2.5.4.11415 (via chocolatey.org), as mentioned at https://github.com/nextcloud/desktop/issues/978#issuecomment-459704912, also the nextcloud context menu appeared, even without a reboot or starting the owncloud-client even once.

btw:

  • yes, i rebooted the system after every change/install/setting/etc.
  • after uninstalling the owncloud-client, even without revo-uninstaller, the context menu and overlay icons vanished again!
  • and thanks @unix0r for investigating so much and summarizing your findings for all of us!

so IMHO here are at least 2 issues mixed:

  1. the overlay dropbox-topic which is really stupid (thanks MS and dropbox! :angry:)... but i have no idea how it should/can be solved on the nexcloud side.
    EDIT: just a wild guess, but after looking into the registry it seems to be solved like described at https://help.nextcloud.com/t/missing-sync-icons-in-windows-explorer/6610/33 (no idea if this also applies for updating existing installs.)
  2. but if you are "Missing overlay icons and the context menu in a fresh Windows 10", it is an integration-issue where you can't blame dropbox.
    so please @camilasan, have a look at the owncloud-client and why it makes the nextcloud-client work as it is supposed to work, without a 2nd client i don't use/need.
    EDIT: as you can see in the next 2 comments by @rkohser and me, it seems that the Visual C++ 2013 Redistributable is missing in the nextcloud-client installer.

but as a not-windows-expert i stop my guesses and assumptions now and continue to work with my :penguin:. :heart:

From the global README build instructions, it seems the client is compiled with the "Visual Studio 15 2017 Win64" cmake generator.
But I assume from this line
https://github.com/nextcloud/desktop/blob/v2.5.2/shell_integration/windows/OCShellExtensions.sln#L3
that the Shell Extensions are build with Visual Studio 2013, so that's why you need Microsoft Visual C++ 2013 Redistributable (x64) to make it run.

That's why the nextcloud client needs both 2017 and 2013 redistributables. That's weird.

@rkohser i was tempted to write that this does not solve the problem... but indeed it seems to do so, if you install the Visual C++ 2013 Redistributable before installing the nextcloud-client! :tada:
so perhaps the owncloud-client installer doesn't do it any better... just the nextcloud-client installer (or even both) are handling it's dependencies not correctly.

but after a little bit more fiddling around, it seems to me, that the owncloud-client installer brings all its dependencies and nextcloud-client does not... that is why the 2nd workaround is to install both clients.
--> the only thing i still don't get, is: why is after installing Visual C++ 2013 Redistributable a reinstall of the nextcloud-client necessary to make all work, but after installing owncloud-client not... :confused: :question:

I could try to install older versions, edit registers, whatever. But when I simply rebooted the computer the icons appeared and the issue was gone.

Just an update, the issue is still present when installing the 2.6.0 version on a fresh windows 10 pro 64 bits.

To be fair the "Shortcuts"/"Quick Launch Shortcut (N/A)" choice is greyed at componnent choice during the installation ... so the installer seems to know their is an issue 😄

A fresh install of Version 2.6.4stable-Win64 (build 20200303) has still the same problem. No overlay icons are shown.

I've just installed 2.6.4 and the icons show. I don't know what causes this.

Tried with win10 with nextclud-2.6.4 ; the way to make it work for me was to open at least one time the left pane explorer icon of nextcloud expanding the tree, then icons appeared and remains either after reboot
image

@everyone

If you are experiencing issues with your shell overlay icons missing, it might be due to the fact that Windows can only support 11 shell overlay icons at a time (15 icons overall, but OS reserves 4 icons for itself). So with only 11 shell icons, you need to prioritize if you have OneDrive, DropBox, GoogleDrive, TortiseSVN, etc...

I created a Wikipedia page that lists out what Shell Icons's names, their function, for each of the services.
https://en.wikipedia.org/wiki/List_of_Shell_Icon_Overlay_Identifiers

I was able to have Shell Icons for NextCloud, OneDrive, DropBox, and Google Drive, so it fits under the 11 shell icon limit.

[Solved]
I had the same problem all the time. I don´t know how or why my solution worked, but it did.

  1. Download ShellExView v2.01 - Shell Extensions Manager by Nirsoft
  2. Search for "ownCloud overlay handler" and "OCContextMenuHandler Class" (in case context menu is missing too like it was for me)
  3. Make sure all of the six (in my case) entries have the switch on "Diabled" -> "No"
  4. Restart Computer

2020-06-05 12_30_24

For some reason the switches were on "Disabled" -> "Yes" on my computer, so switching them on "No" and restarting the computer made the overlay icons and the context menu visible.

Hope this helps for some of you.

@kermit-frog Just tried your solution with a fresh installed Windows 10 2004 in a virtualbox.
After the installation of nextcloud, the extensions mentioned in your post were already set to "Disabled" "No".

But the problem is still there, no icons, even on a fresh installed Windows System.

Could you try one of our recent daily builds?
https://download.nextcloud.com/desktop/daily/Windows/nextcloud-2.7.0.15523-daily-20200611-Release.exe

I've upgraded our build system this week to use Visual Studio 2019 and now we ship the newer Visual Studio 2015-2019 combined runtime.

While debugging I noticed that this could be somehow related to the old 2017-only VC runtime.

Bildschirmfoto von 2020-06-11 17-38-29

Just tried the daily build and starting nextcloud brings this error.

Just tried the daily build and starting nextcloud brings this error.

That's weird, thanks for reporting. Guess I'll try to reproduce this on a fresh Win 10 VM too.

@unix0r It's the installer, failing to install the VC Runtime and then also failing to register the shell extension DLL responsible for handling the overlay icons.

Below are details how to manually fix it but I've already updated our installer and did a rebuild of our last daily, it worked on a fresh Win 10 VM and the overlay icons were shown after a reboot:
https://download.nextcloud.com/desktop/daily/Windows/nextcloud-2.7.0.15525-daily-20200613-Release.exe

What I did to fix it:

  • After installation I did a reboot, nothing changed.
  • Manually installed the VC Runtime from the NC folder:
    C:\Program Files\Nextcloud\vc_redist.x64.exe
  • NC works but overlay icons are still not shown (reboot doesn't help)
  • Manually registered the DLL:
    Run cmd as Administrator in C:\Program Files\Nextcloud\shellext:
    regsvr32 OCOverlays.dll

Of course this is just a manual workaround and not to be the usual handwork ;-)

I've changed our installer script, noticed that MS changed their Runtime's filenames, like:
vcredist_x64.exe -> vc_redist.x64.exe

The new installer is working.
The icons are displayed after a reboot.
After the reboot there is a cmd window opening and its not closing itself. But the icons are there.
Thank you :-)

Closed.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

andresantacruz picture andresantacruz  ·  3Comments

Engineer-of-Stuff picture Engineer-of-Stuff  ·  3Comments

Ich5003 picture Ich5003  ·  3Comments

jospoortvliet picture jospoortvliet  ·  4Comments

js-d-coder picture js-d-coder  ·  3Comments