after the recent update this is happening while trying to generate new and old *yesterday good* toolpaths Internal CAM kernel error. Please report through your support channel.

[202004112036]

after the recent update this is happening while trying to generate new and old *yesterday good* toolpaths

"Internal CAM kernel error. Please report through your support channel."

and also 

"Failed to load camkernel module."

please help  asap 

[giulio.ranalli]

It is not necessary to provide any support.just allow the user to utilize
the last release that works with W7..I don't believe that it is a
complicated issue..what about, if I don't have to money to buy a W10
package?...it is Pandemic Time.don't forget it..

[seth.madore]

We make a build and we test it as thoroughly as possible on the OS builds we support. We aren't going to conduct testing on builds that not even the OS manufacturer doesn't support....

[giulio.ranalli]

Ok, it is time to change software. many thanks for the support in these
difficult times..

[seth.madore]

Windows 10 is $83 at Wal-Mart 

[giulio.ranalli]

And how much would cost to Autodesk create a section with the lastW7 working
release?...shared among the hundreds of thousand of W7 users?

[alan_ambrose]

OK focusing on the bug, which I think should be very simple to fix...

This occurs for me whenever I select '2D Pocket' CAM module.  The little debug listing is shown below. I'm guessing (as a retired software engineer) that it's a deployment issue and/or an API interface issue with camkernel.exe. Mine is signed ‎16 ‎January ‎2022 01:02:56. Happy to send over logs if you can tell me where they live. No rush ... but I have some CNCing that has been held up for a few days now.

Alan

<<<

Feature flags: setup-sheet-viewer

Debug: Initialization elapsed time: 0 ms

Debug: Writing ironjob to C:\Users\ALANAM~1\AppData\Local\Temp\Fusion360CAM\14468-1\operation7.ironjob

Debug: Writing jobfile to C:\Users\ALANAM~1\AppData\Local\Temp\Fusion360CAM\14468-1\operation7.hsm-job

Debug: Using CAM kernel from: C:\Users\Alan Ambrose\AppData\Local\Autodesk\webdeploy\production\5f961055b6b4e87cb54d819910f25c62ea3df4be\Applications\CAM360\camkernel.exe

Error: Internal CAM kernel error. Please report through your support channel.

Debug:

Debug: Total processing time: 46 ms

Debug: Total elapsed time: 412 ms

Invalidated: Generation failed

>>>

[alan_ambrose]

Also '2D Face' gets the same error, but '2D Bore' is fine.

Alan 

[seth.madore]

@giulio.ranalli it's not hundreds of thousands of Win7 users, it's not even 10's of thousands. Where do you draw the line? An obsolete OS is always going to be an obsolete OS.

[alan_ambrose]

On the policy issue:

(a) I suggest that it wouldn't be a big deal to include Win7 in your integration and test set-up. That would make Autodesk look more professional.

(b)  A feature to hold updates / roll back updates etc would also be a professional feature *for all Autodesk users*. Look at the pickle, for instance, that Microsoft are getting themselves into here:

https://www.zdnet.com/article/microsoft-releases-fix-for-patch-that-broke-vpns-hyper-v-virtual-machi...

- and they *do* have a roll-back feature. It's only a matter of time before Autodesk rolls-out an update that breaks the majority of its customer's workflows.

(c) If the Autodesk dev team *really* don't want to support Win7, then *they need to talk to Autodesk marketing* and:

  + agree an end date and inform all users at least a year in advance.

  + refuse to install and/or run on Win7 after that date.

  + AND don't accept payment from users you know are running on Win7 and/or refund those whose software you have broken.

- that is, *** if Autodesk is happy to accept payment from Win7 users, then it should also provide a professional service to those users ***. I don't think accepting payment and then believing that you somehow have the right to break user's workflows at random is acceptable or professional. 

Alan

[giulio.ranalli]

What's the total of Fusion users ?

[alan_ambrose]

And ... I see Internal CAM kernel error is just a general purpose error saying 'something was bad' and it has a bit of history.

As an ex-software developer, the dev team needs to percolate up more detailed error messages and context. The 'something bad happened' error for any old validation / algorithm / system failure is hopeless both for users, developers and support people. I know that you've been doing this for a decade at least, but now would be a good time to start getting real. You could start by differentiating validation / algorithm / system errors from each other. That way, we would know, for instance, whether we just put in an unlikely value for a CAM parameter or a silent install just broke our build. Then some detailed error messages would be helpful - they would allow us to debug our own problems more often, and, at the same time, reduce your support load.

Alan

[seth.madore]

---

@giulio.ranalli wrote:
What's the total of Fusion users ?

---

I'm sorry, we can't publicly share those numbers.

[giulio.ranalli]

considering that the young guys that just arrived to cad cam ( I start with the cad version running in DOS) are using the W10, probably on a laptop, I estimate ( and I can't show you the algorithm ) that 30-40 % of Fusion Users are still working with W7.....would not be worthwhile just allowing this old Dinosaurs continue using their beloved, stable, solid, trustful, reliable OS?.... they will be extincted in a decade or two, anyway....why have to use the W10 meteorite for to accelerate the process.....???

[mikko.husari]

Quick note, we are now running (in new windows10 machine) the "admin installation" method and it seems to provide older version than the problematic one. We got this: 2.0.11415 and according to release notes (the blog) newest version was released 18th of january with a version number: 2.0.12157. I realized this as we were trying to open one design that was last saved on 14th of january. Latest version at that time was probably 2.0.11680.

So, the admin installer is lagging behind... (which is good, just so we can do dry runs on updates before messing up our production).

[seth.madore]

---

@giulio.ranalli wrote:

I estimate ( and I can't show you the algorithm ) that 30-40 % of Fusion Users are still working with W7.....

---

Your estimate is extremely high, by a large amount (yes, we have analytics). As stated previously, we notified users almost 2 years ago (Feb 6th, 2020) about the decision. Any user that chose to continue to remain on Win7 was doing it at their own peril.

[peterhartwich62]

Hello,

The statement regarding the support Windows 7 by Microsoft is not correct !!!

Microsoft supports the ESU Program Windows 7 "Extended Security Updates 2022: January 12, 2022 - January 10, 2023".

Therefore, I can not understand the procedure of Autodesk at all.

Many companies operate Windows 7 calculator until January 2023.

[georgegt18]

Same issue here, also running windows 7. why change to win i don t want !!! i have to change and pay for other programs that i am using. i have a lot of work to do and now you are costing me some money for the delay...please fix that issue!!!

[giulio.ranalli]

with 23$ I bought an HD with w10 installed, and put it on an old PC, so, now I model in W7, with my beast PC, and then  create  the tool-path in the other machine...quite  ridiculous  ah??.....

[jsn.burns]

I just bought another SSD to throw a copy of Win 10 on. Back to having a dual boot system I guess...
My main rig isn't used for just design. With fairly pricey external hardware for those other tasks and drivers that do not work with Win 10 it never made sense to upgrade until my whole system needs it. 
Would just be nice if there were a legacy version, even a standalone one or whatever, since not everyone needs more than the basic modeling and tool path generation. Just unfortunate I guess, that forced obsolescence is part of the subscription scheme.  

[a.sonnette]

Hello all,

After I get same problem as OP (problem with CAM on windows 7 after update despite it was working perfectly the day before...) I come to this subject to read haughty answers from Autodesk. If people, whatever the reason, still wants to stay on win7, PLEASE, just stop update their Fusion360 (like all REALLY professional do), let them use the old version as is, without new features or updates, and stop hiding behind "the windows 7 fault".

That being said, I decided to investigate and compare each dll from Fusion 360 on win10 and win7. After some testing, I simply copy the camkernel.dll from the Fusion 360 on win10 and paste it to replace camkernel.dll in Fusion 360 win7 version, and now it's working perfectly (at least until new update I guess...)

The dll is in a folder named "CAM360" (just use windows search function). Of course, you need a win10 PC to scavenge the working camkernel.dll, but I can provide it if needed.

Hope this work for people experiencing this problem, whatever, I just tested Freecad, and the last version allows to do the same as fusion 360, so my society is changing for Freecad (and addons are numerous and it is open... and FREE).

Have a nice day !