After prolonged use by Linux  of a shared NTFS drive in dual boot, Windows will report a corrupt disk, file system.

There is actually nothing wrong. Linux leaves the shared NTFS drive dirty on purpose to avoid file system corruption by windows fastboot.  Over time of dual booting and not fixing then you might get some corruption.

If you have been using linux for a while then dual boot into windows 8 or 10, then do a disk check of your shared NTFS drive.  Disk check will find errors, fix them, usually without any data loss.

You could turn off fastboot in windows to stop this happening. You could also disk check in windows regularly to fix the dirty flags, without disabling fastboot. That is up to you.

Comment if you need more information.

 

BaDbod

MSI installers, failing signed key. No encrypted or compressed temp folders. Windows 10 and a shared drive with Linux?

internal error 2755, 110  ?

If your sharing a NTFS drive with both windows and linux, then you may well lose some permissions on folders in the shared NTFS drive.

Even i f you are not sharing a NTFS drive in a dual boot system with windows 10 and linux yet you have these symptoms..

internal error 2755. 110  or ‘cannot open device or file specified’.

If you have already done the google and noticed you have no encrypted folders or files, then probably your linux  is stripping some permissions from your dual boot shared drive.

Easy fix.

Where you download your files,

1. Right click your downloads folder and -> properties
2. Security tab
3. Advanced
4. Enable inheritance
5. Apply

If your more with the security angle,  then  make sure SYSTEM has some access.

 

Easier fix?

Another option is to copy the installer files to your windows boot drive. They will install fine from there without you having to mess with your shared drive permissions.

Nod,

BaDboD