Category Archives: Windows 10

NTFS disk corruption, dual boot, linux (ubuntu,mint etc) windows 8, windows 10. Shared disk NTFS.

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

Windows 10, Install error, cannot open device or file, internal error 2755. 110, Shared dual boot, linux windows drive

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

No host to guest network in VirtualBox 5.0.4. Windows 10 host.

The 5.0.4 update for VirtualBox now makes VirtualBox usable under windows 10.

If your using bridged networking and cannot connect from host to guest machines. Go into your Windows 10 host LAN settings and tick or untick IPv6 and Apply. If it still isn’t working got back and tick or untick IPv6 again and Apply.

Enjoy 🙂

[update]
Version 5.0.6 appears to have fixed the problem. Make sure to upgrade. If you are using a version greater than this and still expeiriencing this issue, then please visit the VirtualBox Forums.
[/update]

Windows 10 will not sleep or wakes up for no reason.

Watch this space. Currently no fix for this. You have to shutdown if you don’t want your computer and monitor on all night.

Windows 10 also has a problem with some devices even preventing the screensaver. Unplug joysticks etc, or just shutdown.

I’ll update when there is a fix or workaround.

UPDATE

as of 29/8/2015, update KB3081448 or KB3081452 or KB3081449 (they don’t tell you what they fix) seems to have fixed the sleep problem.

Ill keep you updated.

UPDATE

NOT fixed. Now does go to sleep, then wakes up within 10 or 20 seconds.

UPDATE

If you disable all wake events (power) it will sleep now. Still wakes up when it feels like it, but seems to be improving.

UPDATE
in device manager find your network device. open properties and on the power tab untick ‘Allow this device to wake the computer’. Computer will now sleep much more reliably.