We're making changes to the Community, so you may have received some notifications - thanks for your patience and welcome back. Learn more here.
Forum Discussion
Windows 10 - Dropbox stopped working a few days ago; won't reinstall - errors in DBGCORE.DLL
Installed Dropbox on Windows 10 Pro about a month ago, and it was working fine until a few days ago.
Dropbox stopped working (no Icon in tool tray; update service and normal service both stopp...
I've fixed the problem :sunglasses:
It appears that the copy of DBGCORE.DLL was damaged in the Windows 'Image' (a part of windows where backups of critical files are kept); Windows wouldn't allow the use of the DLL, and couldn't repair it. I used the following method to fix this:
- Use the Microsoft Windows Media Creation Tool to download a fresh copy of Windows 10 ISO file
- Mount the ISO file (right click on it in Windows Explorer) - it will then appear as if it were a CD inserted into your computer.
- Using Windows Explorer find the file ..\sources\install.esd within the ISO, and copy it out to C:\install.esd (this file contains an image of all the files in Windows)
- Open a Windows Command Prompt as Administrator, navigate to C:\ and issue the following command:
dism /Get-WimInfo /WimFile:install.esd
This will tell you which versions of Windows exist in the ESD file, and the index to access each one (I am using Windows Pro, index 6) - Then extract that version of Windows from the ESD file to create a new Windows Image for your version of Windows only, containing the current versions of all files, again using DISM (replace '6' with the index number for your version of windows, determined above). Type the following, without any carriage returns (it will wrap to a second line in the command prompt)
dism /export-image /SourceImageFile:install.esd /SourceIndex:6 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity - The file C:\install.wim file will now contain a single image, for your version of Windows (with index 1). You can use it to repair the image 'embededed' in your windows install using the following command:
DISM /online /cleanup-image /restorehealth /source:WIM:c:\install.wim:1 /LimitAccess - You then need to use the repaired Windows image to repair the installation - you do this as follows:
SFC /SCANNOW - You can check What repairs were done by looking in the file C:\Windows\Logs\CBS\CBS.log. Also, if you had run this command first, it would have told you that the files were corrupt, and couldn't be repaired.
- Then install DropBox!
Thanks to everyone who tried to help here - I found the details of how to do the above repair by searching elsewhere on the web, but special thanks to www.wintips.org where I discovered how to create my own WIM file (which is critical if your windows installation is corrupted). I think the problem was originally somehow caused by a windows update that went wrong...hopefully this may help someone else
-Steve
Jay
Dropbox Staff
Dropbox StaffHi TheFixer, thanks for taking the time to message us!
What error do you get when attempting to uninstall the Dropbox desktop application?
Have you tried the steps in the advanced reinstall page to see if they help?
A screenshot of the error message you're getting would help greatly!
Hi - thanks for the quick reply.
I had forgotten to mention. After one of the multiple failed attempts to install (and also de-install) I went back to the Windows Control Panel and re-attempted a de-install from Programs and Features. That worked (so at the moment I do NOT have DropBox installed)
I have just gone to the 'advanced uninstall' instructions above, and removed the various appdata folders (there were no DropBox folders under ProgramFiles or ProgramFiles x86.
Edit: Having problems getting the images to display in the correct order below - but hopefully the captions make it clear the order they appear in 'Error 2' is the last one.
I then re-attempted the installation, and get the following (same as before)
This appears the moment install startsAnd finally this.Then this appearsand appears about 6 more times
- Jay
When you uninstall Dropbox, do you also get the option to uninstall the DropboxUpdate app? Did you reboot your machine when you uninstalled the app?
Regarding the error 2 message, could you try the steps in this post to resolve it?
I don't recall if there was a separate prompt to uninstall the dropboxupdate app (but I'm pretty certain there wasn't)
I have just checked those instructions for 'Error 2'; neither of the program files folders exist, but there IS a log file for the installer - contents below. Notice that it appears to have reported an issue with a DLL also (last line)
!! dropbox: assigning process to named job object dbx5224
!! dropbox: assigned process to named job object with handle 00000218
dropbox: loading watchdog
dropbox: loaded watchdog. executing watchdog_main
dropbox: starting main app
dropbox: package full name is <unpackaged>
dropbox: initializing
dropbox: initializing python 3.7.9
dropbox: setting program path 'C:\Program Files (x86)\Dropbox\Client_110.4.458\Dropbox.exe'
dropbox: setting python path 'C:\Program Files (x86)\Dropbox\Client_110.4.458\110.4.458;C:\Program Files (x86)\Dropbox\Client_110.4.458\110.4.458\python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: enabling allocator metrics
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension 'C:\\Program Files (x86)\\Dropbox\\Client_110.4.458\\110.4.458\\tornado.speedups.cp37-win32.pyd'
dropbox: load fq extension 'C:\\Program Files (x86)\\Dropbox\\Client_110.4.458\\110.4.458\\cryptography.hazmat.bindings._constant_time.cp37-win32.pyd'
dropbox: load fq extension 'C:\\Program Files (x86)\\Dropbox\\Client_110.4.458\\110.4.458\\cryptography.hazmat.bindings._openssl.cp37-win32.pyd'
dropbox: load fq extension 'C:\\Program Files (x86)\\Dropbox\\Client_110.4.458\\110.4.458\\cryptography.hazmat.bindings._padding.cp37-win32.pyd'
dropbox: load fq extension 'C:\\Program Files (x86)\\Dropbox\\Client_110.4.458\\110.4.458\\psutil._psutil_windows.cp37-win32.pyd'
dropbox: load fq extension 'C:\\Program Files (x86)\\Dropbox\\Client_110.4.458\\110.4.458\\apex._apex.cp37-win32.pyd'
dropbox: load fq extension 'C:\\Program Files (x86)\\Dropbox\\Client_110.4.458\\110.4.458\\win32com.shell.shell.cp37-win32.pyd'
Traceback (most recent call last):
File "dropbox\client\main.pyc", line 49, in <module>
File "dropbox\app\machine_anchor.pyc", line 8, in <module>
File "dropbox\client\features\apollo_metrics_reporter\__init__.pyc", line 17, in <module>
File "dropbox\client\features\apollo_gating\__init__.pyc", line 11, in <module>
File "dropbox\foundation\html_views\common\__init__.pyc", line 39, in <module>
File "dropbox\foundation\html_views\common\js_scripts.pyc", line 21, in <module>
File "dropbox\foundation\html_views\bridge\impl.pyc", line 75, in <module>
File "dropbox\foundation\html_views\common\threading.pyc", line 16, in <module>
File "dropbox\client\ui\common\uikit.pyc", line 43, in <module>
File "dropbox\client\util\__init__.pyc", line 142, in <module>
File "dropbox\client\util\win.pyc", line 117, in <module>
File "winffi\dbghelp\api.pyc", line 6, in <module>
ImportError: DLL load failed: %1 is not a valid Win32 application.- Walter
Hey there TheFixer; I'm sorry to jump in here, but could you ensure that you're installing the app with admin privileges on the affected computer?
If there are any pending OS updates as well, please apply them to make sure your machine is up to date.
