On Sun, 01 Jul 2018 15:16:23 -0400, Nil
wrote:

It seems to be difficult to delete.

Resistance is futile. Or, even for Microsoft, rather ironically,
General Public Licensing has GRUB pretty much written in bold Bull's
Eye lettering on the wall. (Excluding one of Windows 10's recent
patches which "broke" GRUB.)

https://en.wikipedia.org/wiki/Compar...f_boot_loaders

NTFS then being somewhat a minor imposition for "static" maintenance.
"Ghosting", or imagining software capable of advanced editing within
its own images. Although few do among those that will well cost.

Operational VM system imaging and a 128M/Byte developer's platform
would be another interesting scenario.

Another is to zero it out, a null overwrite. A proviso of Microsoft
coding for looping validity and a prior state of counters.dat to
intermediary accountability -- in extremity the infamous "blue" or
other errant form of terminable screen.

As any type of CCleaner sort knows, among degrees of severity these
programs attempt, that results are not to be held accountable for data
loss, when a standard user assumes responsibility to contain their
system for events of failure.

Or, none of the above: Microsoft operates at "levels" of associative
permission permitted modular modifications. A core modular or highest
system-level being both impermissible and proprietary, if all but
inured (sic) by dint of US Copyright.

When 'difficulty' is another informality and hardly anything but
easier a second time up. (Unless perhaps a preclusion by another
formality, such as a scrutiny for Windows' "programs" given leeway by
code-writers of WINE.)