Windows 10: Writing text files via script are corrupted

I've just upgraded a computer from the previous Win10 to Win10 AE.
I have a compiled AutoIt script which I use to read in text files from a folder and write them out again after modifications. This has worked for years.
The files were partially corrupted today. I repeated it to check.

Moving the files and script to another computer (earlier Win10), it ran fine.

I doubt there would have been a change to how Windows reads and writes to the file system??
I'll ask in the AutoIt forum, as they may have an idea of what's happening.

:)

 

Create a PowerShell script to create a copy

Which part are you having issue with?



Writing the powershell script or calling it via a scheduled task?

 

Windows Update error - status: 0x80070003, failure source: DOQ?

Hi folks,



We're investigating a case of a registry corruption that sometimes occurs on Windows 10 (1511) systems. Systems with this problem run into an error while trying to install updates. At this time the reason for the corruption
is not fully understood, but it may be the result of a third-party tool of some kind.



(If your CBS.log file shows status: 0x80070003, failure source: DOQ you might be experiencing this problem.)



We are working on a tool to try to solve this, which would enable you to update your computer. We're hoping that you can help us gather some data to refine our tool.



If your Windows 10 (1511) system is unable to take the latest updates, we'd love it if you'd run the below script to see if you are encountering this particular problem. The script doesn't change the state of your
system in any way, it just scans some log files, filters on some specific error patterns, and checks if corresponding files are present in the system's driver store.



Here's how to run the script:

1. Press Windows-R and run powershell.exe

2. Paste the below script into the Powershell window and press Enter

3. If the script indicates you have the problem, let me know!



Please note: It's okay if the script gives a red "ObjectNotFound" error, just so long as it doesn't say at the end that corruption was found.



Below is the script. As always, your help is greatly appreciated! - John Wink [MSFT]



$issuefound = $false

$files = gci $env:windir\inf\setupapi*.log

$errors = $files | Select-String "!!! *inf: *Invalid INF '.*', parsing error on line 0. Code = 1002"

$infs = $errors -Replace ".*!!! *inf: *Invalid INF '(.*)', parsing error on line 0. Code = 1002",'$1' | Sort-Object -Unique

foreach ($inf in $infs) {

if (-not (Test-Path $inf)) {

Write-Warning "Please contact Microsoft, corruption found in $inf"

$issuefound = $true

}

}

if (-not $issuefound) {

Write-Host "Registry Corruption issue not found. Thanks for your time"

}