This is a registry issue. One person in the office had it as well. I will ask him how he got rid of it.
*Edit*
I just checked. Cura constantly checks for removable drives. Windows tells cura that that drive is a removable drive. When cura tries to open it, windows gives an error, which Cura never hears about.
Renaming the drive should resolve the issue (I know, it's a weird & stupid solution...)
Edited by GuestWhy does Cura try to open it in the first place?
I renamed the drive from "USB Drive" to just "Goop" and it still throws that error box.
I don't know of any way to change the Drive Letter short of going into the Hardware config and modifying it there - I'd prefer not to do that.
Also, Cura 2.3.x never did this...
P.S. More Info: After getting Cura started, I noticed that its 'Save' button is defaulting to 'Save to Removeable Drive'. I believe in previous versions it would default to the last drive and path you saved your gcode to. It doesn't appear to be doing that anymore. I can save the gcode to my HD and then exit and restart Cura, but it goes right back to 'Save to Removeable Drive'.
The only way I've found to get around this is to a) put an SD card in the drive before booting Cura, or b) unplugging my SD Card reader. A workaround for now, but not a solution.
Edited by GuestWhy does Cura try to open it in the first place?
User convenience. Most people tend to save things to SD & USB drive. So having an easy option to do it (and provide an eject option) makes their lives easier.
I don't know of any way to change the Drive Letter short of going into the Hardware config and modifying it there - I'd prefer not to do that.
I understand, but as I said, it's a nasty fix.
Also, Cura 2.3.x never did this...
The colleague I talked with had this for quite a long time. We didn't change anything in the code that does this for quite a while, so it's hard for me to explain (or even know) how this suddenly is an issue. It seems more likely that it's something on your system that is changed (Sounds like an easy answer from my end though...)
P.S. More Info: After getting Cura started, I noticed that its 'Save' button is defaulting to 'Save to Removeable Drive'.
This has been default behavior since Cura 2.1. It's weird that you never had this before. It does strenghten my hypotheses that something on your end changed somehow...
I reinstalled Cura 2.3.0 beta along with wiping out the "C:\Users\[MyName]\AppData\Local" folder and it started with no issues.
Doing the same routine with 2.4.0 give me those "There is No Disk..." dialogs.
I'm gonna dig around some more....
P.S. Keep forgetting to mention: The first launch of Cura 2.4.0 after install goes without any issues. It's only after closing it and launching it again that those pesky dialogs appear.
Edited by GuestOk. The only thing I can figure is that Cura is making some Registry Change on the first launch of it. Is there a list somewhere of all the Windows Registry Entries Cura makes/changes on the install/first launch?
The reason I say this is because:
So its nothing to do with the \AppData\cura folder or changes made in \Program Files\Cura 2.4 folder, so I has to be in the Registry.
@nallath, can you point me in the direction of these registry entries?
Thanks!
@nallath, can you point me in the direction of these registry entries?
As far as I know, Cura doesn't make any registry entries (apart from file association)
I too am seeing behavior that would indicate that data is stored outside of the \AppData\cura folder.
I've posted my info here:
https://ultimaker.com/en/community/38963-cura-24-issues
Basically I am deleting the \AppData\cura and installing new, and when I add printers back I get ghostly instances for Material Profiles.
I've been experiencing the exact problem for just the last day. Cura had become completely unusable. Here's how I remedied the problem on Windows 10 Pro.
Open the Control Panel. Choose File Explorer Options. Choose the View tab. Choose the radio button "Show hidden files and folders, and drives"
Click Apply.
Now when you open This PC you may see an otherwise hidden D Drive. In my case it actually displayed as a greyed out Removable Disk (D:). It may also show up as a greyed out USB Drive (D:). In any case, put a device into the slot or port, or reassign the drive letter by using the Disk Management
Hope this helps somebody . . .
Same issue here.
Windows 8.1, Cura 2.4.0
It's only the D drive for me. I have many other removable disks (and actually the SD card is normally the J drive), but only the D (DVD) drive is getting flagged.
Cura has become unusable. Change layer height, accidentally move model, drop new model on workspace, do almost anything and I get 50+ no disk messages.
I'm going to roll back to 2.3.1, hopefully a fixed build of 2.4 will be out soon?
FYI: This is still broke in 2.5.0beta
Found a solution. Go into disk management (dskmgr.msc, or simply search "disk management" in the start menu), find drive D: in the bottom half of the window, right-click > change drive letter and paths > select D: in the list and click remove. Afterwards you shouldn't get the error anymore. For some reason, Cura just cant accept that my SD card reader is empty and that it should give up on trying to read from it.
Found a solution. Go into disk management (dskmgr.msc, or simply search "disk management" in the start menu), find drive D: in the bottom half of the window, right-click > change drive letter and paths > select D: in the list and click remove. Afterwards you shouldn't get the error anymore. For some reason, Cura just cant accept that my SD card reader is empty and that it should give up on trying to read from it.
So then your SD Drive is gone and you cannot use it anymore?
I need my SD Drive more than Cura. Not going to hobble my PC. It worked fine in 2.3
I have Cura 2.5.0. Used once. Next time insists:
Please insert a disk in to drive D:
My SD card is G: and I have never saved to it from Cura.
I'm using Windows 10 v1607.
Sorry, this is definitely a Cura problem if it happens on multiple machines.
The bigger oversight is that neither cancel nor the continue work. The former should exit the app the latter should skip past the error!
Please fix.
I appreciate that you have done a lot of work on this version 2 code but sorry again, I still think that Cura 15.04 is the more reliable code base.
Having read a few more forums where this problem is reported:
https://github.com/Ultimaker/Cura/issues/1022
It appears it is caused because unused USB card readers and probably built in ones, report that the drive letter exists but if you try to use it you get the error.
All that needs to be done is to test the drive BEFORE Windows can throw up the error. If the drive is not usable, then launch the programme without the previously used drive being read.
Edited by GuestI don't know what changed in Cura, but this did not happen with 2.3.0 and before.
I have the same problem. Windows 10 with creators update. I was using 2.3.1 no problems. Installed 2.5 and it started after installation, but i get the same insert disk message when trying to start it again. I uninstaled all versions of cura and local app data and any additional files i could locate. Downloaded a fresh 2.5, disabled anti virus and firewalls and installed as administrator. It ran from the install complete screen again then when attempting to start again i get the same insert disk error if you repeatedly press continue it will eventually run, but during use i periodically get the insert disk message and have to repeatedly press continue until it clears. If anyone has a solution i would appreciate it.
If anyone has a solution i would appreciate it.
Well, how about installing VirtualBox and a Linux system and then you can use the Linux version of Cura which doesn't suffer from this problem. Better still, ditch Windows and just use Cura on Linux. I'm only kidding folks but if you're really pulling your hair out over this, maybe it's worth considering...
hi
i have the same problem ...for me the solution was:
disconnected an USB dongle named D and launch cura .
Could you tell the exact brand and model? Perhaps someone can reproduce and fix the issue if we find that reader/dongle.
Well the odd part, as I said before, is that this didn't start happening until 2.4. Before that, I didn't have this issue.
Here's a SD Card reader that works in 2.3, but fails with 'No Disk...' in later versions:
xoopar
Model: XP31004
https://item.taobao.com/item.htm?id=524094473354
Windows Info:
Alcor Micro USB 2.0 Card Reader
Driver Provider: Alcor Micro, Corp
Driver Date: 7/13/2015
Driver Version: 1.0.114.20101
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Hope this helps.
Does not appear to be on Amazon. So apologies for the obscurity.
A little history: So I wore out my built-in SD Card reader with all the in-n-outs (yes, I can hear you snickering...) and bought this USB one to replace it (it has a built-in USB slot as well). Now, I really don't want to wear out my 1 of only 2 USB plugs by constantly plugging/unplugging the reader every time I want to use Cura. If I wear the external USB card reader out, I can't just buy another one - cheaper than a new laptop...
I have the same problems with 2.4 and 2.5, version 2.3.1 ran perfect.
I just reinstalled 2.5, and (using info from this discussion) had an SD card in the D drive (I never use that drive, the box sits in a hard to reach place, I have a USB-wired external SD drive). Now it works when I double click on an .STL file, no problem.
Little but: the "save" is now automatically to the D drive, with the SD card that I stuck in. That is a choice you can override.
(bloody browser, it is a D: drive but I have to call it a D drive :-(
Edited by GuestCan you try removing the Cura 2.5/plugins/RemovableDriveOutputDevice and see if the issue remains?
I have a hunch. Can you try changing the drive letter from D to another drive letter?
Hey there, I have a short term fix for creators edition.I have the same problem. Windows 10 with creators update. I was using 2.3.1 no problems. Installed 2.5 and it started after installation, but i get the same insert disk message when trying to start it again. I uninstaled all versions of cura and local app data and any additional files i could locate. Downloaded a fresh 2.5, disabled anti virus and firewalls and installed as administrator. It ran from the install complete screen again then when attempting to start again i get the same insert disk error if you repeatedly press continue it will eventually run, but during use i periodically get the insert disk message and have to repeatedly press continue until it clears. If anyone has a solution i would appreciate it.
1) make sure your are Admin of the machine.
2) right click start menu and choose disk managment.
3) Find Physical Disk that has "D Drive" as its populated address (noted there is actually no partition.
4) go to the propteries of the physical and reassign the drive to say "Y:"
Go start Cura.
ArunC posted a topic in UltiMaker Cura,
.thumb.jpeg.0b7a05eafc09add17b8338efde5852e9.jpeg)
Dustin posted a topic in Firmware,
Recommended Posts
DaHai8 74
Correction: Clicking on 'Cancel' 158 times finally gets Cura up and running.
When closing Cura, I get the same dialog box and must click on 'Cancel' 2x to quit.
Here's that log file:
2017-02-22 13:34:19,783 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin FileLogger2017-02-22 13:34:20,671 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin GCodeProfileReader2017-02-22 13:34:21,567 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin GCodeWriter2017-02-22 13:34:22,432 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin ImageReader2017-02-22 13:34:23,209 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin LayerView2017-02-22 13:34:24,320 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin LegacyProfileReader2017-02-22 13:34:25,209 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin LocalFileOutputDevice2017-02-22 13:34:26,104 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin MachineSettingsAction2017-02-22 13:34:26,896 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin PerObjectSettingsTool2017-02-22 13:34:27,745 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin PostProcessingPlugin2017-02-22 13:34:28,664 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin RemovableDriveOutputDevice2017-02-22 13:34:29,593 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin SliceInfoPlugin2017-02-22 13:34:30,497 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin SolidView2017-02-22 13:34:31,441 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin CameraTool2017-02-22 13:34:32,474 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin MirrorTool2017-02-22 13:34:33,690 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin RotateTool2017-02-22 13:34:34,593 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin ScaleTool2017-02-22 13:34:35,521 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin SelectionTool2017-02-22 13:34:36,474 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin TranslateTool2017-02-22 13:34:37,393 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin UltimakerMachineActions2017-02-22 13:34:38,521 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin UM3NetworkPrinting2017-02-22 13:34:38,666 - INFO - UpdateChecker.UpdateChecker.run [40]: Checking for new version of cura2017-02-22 13:34:39,602 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin UpdateChecker2017-02-22 13:34:40,545 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin USBPrinting2017-02-22 13:34:41,530 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin VersionUpgrade21to222017-02-22 13:34:42,730 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin VersionUpgrade22to242017-02-22 13:34:43,794 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin SimpleView2017-02-22 13:34:44,834 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin WireframeView2017-02-22 13:34:45,754 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin X3DReader2017-02-22 13:34:46,754 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin XmlMaterialProfile2017-02-22 13:34:47,635 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin XRayView2017-02-22 13:34:48,619 - INFO - UM.Qt.QtApplication.__init__ [90]: Command line arguments: {'disable-textures': False, 'file': [], 'external-backend': False}2017-02-22 13:34:49,595 - INFO - UM.VersionUpgradeManager.upgrade [100]: Looking for old configuration files to upgrade.2017-02-22 13:34:50,515 - DEBUG - UM.Backend.Backend._logSocketState [167]: Socket state changed to Listening2017-02-22 13:34:51,476 - INFO - UM.Backend.Backend.startEngine [71]: Started engine process: C:\Program Files\Cura 2.4\CuraEngine.exe2017-02-22 13:34:52,452 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] Calling engine with: ['C:\\Program Files\\Cura 2.4\\CuraEngine.exe', 'connect', '127.0.0.1:49674', '-j', 'C:\\Program Files\\Cura 2.4\\resources\\definitions\\fdmprinter.def.json', '']2017-02-22 13:34:54,347 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] 2017-02-22 13:34:54,747 - DEBUG - UM.Backend.Backend._logSocketState [171]: Socket state changed to Connected2017-02-22 13:34:56,027 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] Cura_SteamEngine version DEV2017-02-22 13:34:56,475 - DEBUG - UM.Backend.Backend._onSocketStateChanged [161]: Backend connected on port 496742017-02-22 13:34:56,589 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to ultimaker3; Multi-extrusion printers are not supported2017-02-22 13:34:57,382 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] Copyright © 2014 David Braam2017-02-22 13:34:58,314 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] 2017-02-22 13:34:58,554 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to ultimaker_original_dual; Multi-extrusion printers are not supported2017-02-22 13:34:58,953 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to punchtec_connect_xl; Multi-extrusion printers are not supported2017-02-22 13:34:59,183 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to ord; Multi-extrusion printers are not supported2017-02-22 13:34:59,405 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] This program is free software: you can redistribute it and/or modify2017-02-22 13:34:59,557 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to ultimaker3_extended; Multi-extrusion printers are not supported2017-02-22 13:35:00,588 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] it under the terms of the GNU Affero General Public License as published by2017-02-22 13:35:01,676 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] the Free Software Foundation, either version 3 of the License, or2017-02-22 13:35:02,632 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] (at your option) any later version.2017-02-22 13:35:03,568 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] 2017-02-22 13:35:04,521 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] This program is distributed in the hope that it will be useful,2017-02-22 13:35:05,559 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] but WITHOUT ANY WARRANTY; without even the implied warranty of2017-02-22 13:35:06,552 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the2017-02-22 13:35:07,469 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] GNU Affero General Public License for more details.2017-02-22 13:35:08,529 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] 2017-02-22 13:35:09,496 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] You should have received a copy of the GNU Affero General Public License2017-02-22 13:35:10,490 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] along with this program. If not, see .2017-02-22 13:35:11,468 - DEBUG - UM.Controller.setActiveView [81]: Setting active view to SolidView2017-02-22 13:35:12,468 - WARNING - cura.Settings.ExtruderManager.getMachineExtruders [375]: Tried to get the extruder trains for machine Prusa i3 Mk2, which doesn't exist.2017-02-22 13:35:13,402 - WARNING - cura.Settings.ExtruderManager.getMachineExtruders [375]: Tried to get the extruder trains for machine Prusa i3 Mk2, which doesn't exist.2017-02-22 13:35:15,707 - DEBUG - UM.Mesh.MeshData.calculateNormalsFromVertices [379]: Calculating normals took 0.006003618240356445 seconds2017-02-22 13:35:15,709 - DEBUG - STLReader.STLReader.read [63]: Loaded a mesh with 8052 vertices2017-02-22 13:35:16,274 - DEBUG - UM.Qt.Bindings.Theme.load [126]: Loading theme file: C:\Program Files\Cura 2.4\resources\themes\cura\theme.json2017-02-22 13:35:17,427 - DEBUG - UM.Qt.Bindings.Theme.load [186]: Loaded theme C:\Program Files\Cura 2.4\resources\themes\cura2017-02-22 13:35:18,073 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action._createAdditionalComponentsView [134]: Creating additional ui components for UM3.2017-02-22 13:35:19,735 - DEBUG - UM.Mesh.MeshData.approximateConvexHull [347]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.004003047943115234 seconds. 36 input vertices. 36 output vertices.2017-02-22 13:35:19,742 - DEBUG - CuraEngineBackend.CuraEngineBackend.slice [152]: Starting slice job...2017-02-22 13:35:21,503 - DEBUG - UM.Qt.GL.QtOpenGL.__init__ [57]: Initialized OpenGL subsystems.2017-02-22 13:35:22,824 - DEBUG - UM.Qt.GL.QtOpenGL.__init__ [58]: OpenGL Version: 4.0.0 - Build 10.18.10.43582017-02-22 13:35:24,327 - DEBUG - UM.Qt.GL.QtOpenGL.__init__ [59]: OpenGL Vendor: Intel2017-02-22 13:35:25,641 - DEBUG - UM.Qt.GL.QtOpenGL.__init__ [60]: OpenGL Renderer: Intel® HD Graphics 40002017-02-22 13:35:35,768 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles2017-02-22 13:37:34,415 - DEBUG - UM.Qt.QtApplication.windowClosed [198]: Shutting down cura2017-02-22 13:37:34,730 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [197]: Attempting to kill the engine process2017-02-22 13:37:34,731 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [203]: Killing engine process2017-02-22 13:37:34,735 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [206]: Engine process is killed. Received return code 1Link to post
Share on other sites