Windows 10: Win10 NTFS file copy/backup utility that handles permissions correctly

Yup, the "canned" solutions generally don't work, especially in attempting to fix fundamentally flawed architecture.

Haven't played with this, but I suspect it's not the immediate concern. I'm running Win10 Pro. The two or so other Win10 Pro systems I have are doing WU just fine, presumably using the same default policies. This server got data corruption probably because of some recent power-outages that outlasted the UPS.

I don't play with policies much, as these are my home machines. But, perhaps the info would enlighten me as to what settings are involved.

As I've mentioned, at this point a live-DVD or alternate OS repair mechanism makes much more sense. The "damaged" NTFS file system shouldn't be used to fix itself. Too many things locking up on themselves, especially with the convoluted Microsoft "enhanced" protection mechanisms.

On another of my Win10 systems, the "we'll replace your driver regardless" policy was such a joke, as the specific (Win7) driver for a wireless device I had worked perfectly and Win10 in its infinite wisdom kept on replacing it with a newer but bad one, breaking my network connectivity. Granted that the device vendor screwed up its device ID, but there was no way to say "no" to Win10.

Perhaps I'll try this, using my cloned drive (as I don't want to mess up my running drive).

But, running the repair tools in the Windows install DVD should have not needed any of these things.

Thanks for your and everybodies else's help.

As of now, I'm resigned to use a crippled system...

 

We're adding three screenshots that are all self explanatory, and we hope the settings illustrated are helpful to a lot of people and of course you yourself @Win10 User. Microsoft undoubtedly needs to do something about its quality assurance, and these workarounds have been extremely helpful to us. If they also help you, please just pay it forward and help others with the same info. *Biggrin

Screen shots as follows:

Disabling Defective Windows Defender - Anti-Exploit Module in Windows 10 Group Policy





Known working Windows Updates Configuration through Group Policy for Windows 10:





Disabling Defective Windows Defender Modules in Registry (Includes WdNisSvc)





There are some other Group Policies to consider for Windows Defender, so we threw together a little slide show. Hope these additional screen shots are helpful.

https://drive.google.com/drive/folde...o1VMR9BCCmJn-n

Please understand one key thing about these settings, we do use our own anti-virus and anti-malware services, and it's not advised to use the configuration that we do without some sort of other anti-virus and anti-malware services and/or protection software present, but at least most anti-virus programs that are commonly and unrelated to Microsoft actually work properly.

May these be a way out for some of the issues happening, and we hope they help.

Best Always,

SLI - IT-IS Team

 

@StepLadderInc

Thanks for sharing all these GP configurations. Highly appreciated.


Would it be possible to make a copy of the slides at Google drive and upload them here for archiving purposes? Would help many in the future. Files shared on external sources tend to get lost with time.


...just an idea... *Smile

 

@slicendice - Can do, we always check them first, and just finished doing that using our GSync service on our public account that we only use specifically for this type of purpose. They're all in perfect order.

As you can tell, some of our formatting is a bit on the imperfect side, but we're quickly adapting to the type of formatting appropriate to Ten Forums. Any suggestions on the best way to upload that many files in a slide show onto Ten Forums so it doesn't monopolize a page because that's a lot of screen shots?

Please let us know the best way to share them directly.

Thanks.

SLI - IT-IS Team

 

As requested, the whole enchilada. *Biggrin It's our sincere hope this was ok to do, and if not for some reason, always open to suggestions, just please PM them. Thank you.

Best Always,

SLI - IT-IS Team

 

Is this some sort of joke?

I'm fairly sure that MS have a better grip on making a new file system than you lot.

 

I think he meant that they use 3rd-party AV solutions, not MS built in AV solutions. I don't think he's trying to write a new filesystem, or did I miss something???

 

@lx07 Most of the people here have an average of 20 or more years of professional experience that includes in development and high-end security environments. In light of the work we do, choosing a cross-platform anti-virus service was quite a process; however given the quality of Microsoft's support basically having the vast majority of them being made up of a bunch of actors instead of IT pros, we don't agree with your statement. FYI, we said we had our own services, we never said we developed them ourselves, and we haven't because such a project would be too time consuming, and that's just common sense. We love our anti-virus & anti-malware endpoint provider, the provider is certainly not Microsoft, and our systems have never been compromised in over 20 years, so our track record speaks for itself.

As to knowledge of the file system, we've always been ahead of the curve; for example, all our equipment has used UEFI architecture since 2009, and very few organizations can make the same claim; nor can the vast majority of organizations claim that they've not had a data breach in over a decade. Most of us were working in NT3.5 and even DOS and Unix environments in the 1980's & 1990's and still work in the IT-IS industry.

So, your personal attack was unwarranted, and since there are about 30 people in this department that are part of the week-end maintenance team, you literally just insulted about 30 people without grounds. "Our own services," yes, meaning services we chose after performing significant and time consuming research to choose the right provider, and our provider has been superior to Microsoft in every way for some time, and can also say themselves, that their level of experience is equal to our own; however they can also say that they've had one discipline in their own careers that's solely focused on anti-virus and anti-malware software developments. On our end, we've multiple disciplines on average, so we're not the same as our endpoint provider of anti-virus and anti-malware services; nor do we claim to be.

In short, Microsoft at this time is abusing the trust of its own customers by putting out defective software and claiming it defends systems running its OS; however as such, if the modules for that software where Microsoft is making such claims corrupts data without providing actual defenses, then Microsoft itself has made our point for all of us.

'nough said. *Smile

Best Regards,

SLI - IT-IS Team

"IT personnel using scripts are like actors, 'Oh, I'm not really a technician, but I play one at work.'"

 

OK. Well carry on then. Anyone could of course use robocopy but your rambling is fascinating.

Please tell us more about your services - I'm interested.

 

Well, at least there's some progress.

I didn't look at cbs.log carefully (misled by some Web info), but the log clearly indicated that wrpint.dll was missing/corrupt. I copied a wrpint.dll from another tree in c:\Windows\winsxs\... to the indicated tree and at least "sfc /scannow" ran, indicating no file corruption.

I then ran "dism /online /cleanup-image /scanhealth" and there is an indication that "the component store is repairable."

However, when I ran "dism /online /cleanup-image /restorehealth," dism indicated that I need to use the "/source:" option to provide a local install.wim file. I got the install.esd from the Win10 installation DVD and extracted the install.wim from it (image #8, Win10 pro). So, I then ran "dism /online /clean-image /restorehealth /source:wim:c:\Temp\install.wim:1 /limitaccess" but dism keeps complaining that it can't find the source files. I suspect that the dism.exe I'm using, version 10.0.16299.15 (Image version 10.0.16299.125, whatever this is) has some bug. I have tried all sorts of variations for the "source:" argument. The cbs.log indicates the file is not found. I'd like to attach the last part of cbs.log here, but l only see the insert-image and insert-video buttons.

Anyway, I'll keep experimenting.

 

Windows 10 has become such an embarrassment for Microsoft. Dism is simply broken and, by all accounts of various Web articles, has been so for years. The logs from the maintenance tools, CBS.log, dism.log, etc., don't say anything useful for the user to fix things themselves.

So sad. Win95 had far fewer maintenance nightmares.

 

Recall that I was unable to run "sfc /scannow" when booted off the Windows installation DVD (live-DVD), getting the same "Windows Protection System could not start the repair service" that I was getting when booted off the C: system drive. This can only happen because the software engineers seriously screwed up, and instead of using _only_ the contents of the DVD (usually on ram disk) to run the OS in live-DVD mode, ended up using contents of the (essentially off-line) system drive to run the OS (perhaps because of bad PATH, etc.).

Either some engineers really don't understand how these things work, or the quality assurance folks (if they exist) have become sloppy as sin.

 

Hi folks.

I really can't believe that Ms would willingly put out defective software deliberately - for starters just think (not sure in USA but I'm sure same sort of law exists) in EEA / EU if product is released knowingly defective the consumer has a right to a refund -- just imagine the billions of dollars and law suits that would be going on -- probably there wouldn't be anybody else employed in anything else at all other than litigation.

The applications, hardware and dependence that we have everyday on computers couldn't even have been dreamed about even a few years ago - imagine no amazon, diminished google, no social media, E-commerce, E-learning, Police crime detection- etc etc. The fact that Windows still runs on the majority of the world computers usually without issue is a major achievement in itself. If there were better and easier solutions it would already be out there -- the fact that it isn't must say something.

Yes there are some better solutions for some things but these usually require a decent amount of knowledge to get them implemented - usually way beyond the average user.

The trouble is if Ms changes something that people are used to then there are the inveterate moaners who say why change it. Yes the did (as all big companies do) make a mistake with W8 - an abomination for people who don't regard a computer as an oversized mobile phone.

I do though think though as DATA is increasingly important for not just corporations but for individuals too Ms needs to introduce a more robust journaling File system and get some decent utilities so people can save their data quickly and safely.

The Linux standard RSYNC program (and it's GUI GRSYNC) is in my mind what ROBOCOPY should be like and certainly as I've previously mentioned software RAID should be made usable in Windows too.

Ms isn't in any way "The Evil Empire" some posters on this thread seems to think it is - there are things wrong with it -- concentrate on those rather than take a swipe at the whole corporation.

Cheers
jimbo