Is the scanner software 32 or 64 bit? If it's 32 bit, TB must be 32 bit for the auto attach to work. TB defaults to 64 bit on 64 bit Windows, although 32 bit TB works fine.

Thanks for your reply , I've been using TB with these scanners for some years and the problem only developed some months ago and all 4 Win 10 systems failed to work, no all 4 say theres no TB associated with the scanner to send email to TB, TB currently is 128.2.3esr (32 Bit), I dont know whether the scanner software is 32 or 64bit, how / where can you find out .............. I cant see anywhere on the MP Navigator EX 2.0 about how many bits it is .......

I would look at where the MP software is installed. If it's in Program Files (x86) it's very likely 32 bit. If it's in Program Files, it's probably 64 bit. TB must also be set as the default mail app in Windows Settings. Do the same in TB Settings/General/System Integration.

thanks for your kind reply MP is in X86, TB has been set as default for a few years, TB was set as TB Settings/General/System Integration, still wont auto attach but at least I can make it to that manually, I can only surmise that something has changed in perhaps a microsoft update, either way I give up .................... and will just put up with it

There's one more simple step that might resolve the problem: follow the instructions here.

thanks once again, tried it and didnt fix the issue, I can manually attach scans just wont auto send to TB this is left me wondering if its a Microsoft problem or some other bug, it affects all 4 computers at least with the other 2 I can finally attach scans now to an email , to do this I had to actually point the MP navigator to the TB client from the location in the Progams x86 folder and adding it, thats the only thing that did work, but its still not automatic I have to attached manually, i conclude it may be a Microsoft caused update that stopped the olde canon scanners from working correctly, around the same time I also has a security exception problem with TB who said it also may have been either a Microsodt or Nortons update could be all related ........, thanks for trying it was most appeciated.