Windows 10 October 2018 Update rollout now paused

RingTailCoon said:

That popup you speak of is unknown to me. :) I don't have it!

This one when I temporarily disable Real Time Protection in Windows Defender (I'm using a clean install of 1809 Home by the way).

Keeps popping in from the side, along with a nice little tune. Takes focus priority over everything - even pops up over the top of videos I'm playing in VLC Media Player, etc. Rather annoying, I must say.

I suppose I could disable it by turning off Banners and Sounds but that will also disable notifications when I'm safely removing external USB drives, etc. Now that I've finished setting up all my programs, etc. with 1809 I will probably leave Real Time Protection on now.

jimbo45 said:

Hi folks
on 1809 if you use things like Wintogousb it will fail due to NTFS file compression.
I was using Clone existing system option which has worked absolutely fine in build 1803.

you'll probably get as far as the initial login screen then it will fail -- "Oops something went wrong with driver not loaded or similar -- typical candidates are wpprecorder.sys but could be other drivers. These are compressed

(Note - the standard W10 version 1809 on the internal HDD (SSD in my case) is OK - it's creating a Wintogo with WINTOGOUSB type programs where you get the failure).

What you have to do is try and boot into safe mode (that seems to work) and then disable the compression

Due to something in the 4KB sector advanced format in NTFS

the whole article can be read here :

BSOD system_thread_excption_not_handled (WppRecorder.sys)


Before attempting this I'll have a go with using a FAT32 partition for the WintoGo OS

BTW Wintogousb works perfectly on build 1803.

Ms obviously did change something in the file system -- even Macrium had to get a fix.

Cheers
jimbo

Doing as the article says does not help. What did help was to replace the wpprecorder.sys from 1809 with the one from 1803.

WinTo Go then installed perfectly and is running well. So it seems that wpprecorder.sys in 1809 is somewhat broken.

LEOPEVA64 said:

I already confirmed that the bug exists...

I can confirm that it exists in both the x86 and x64 version of 1809, 17763.55.

There are so few people that use Windows Explorer to extract compressed files that maybe that's why this bug went unnoticed...

I use it all the time, but the bug only hits when you extract a file to somewhere where a file of the same name already exists. Not something I generally do, so I hadn't spotted this one

I use the Built in Zip Extractor all the time, and i even didn't notice this one, or didn't pay much attention i guess, since wasn't important files i was extracting i suppose

Anyday now, I'm on reading week and this is the best time for me to reinstall however the ISO on Microsoft's website is still 1803.

LEOPEVA64 said:

There are so few people that use Windows Explorer to extract compressed files that maybe that's why this bug went unnoticed:

The Windows 10 October 2018 Update has another strange file management issue which could lead to data loss

I already confirmed that the bug exists but I also confirmed that this bug is not present in the Fast ring and Skip Ahead builds, so Microsoft may already know about this bug and they are going to back ported the fix to O18U with a CU as they have done several times in the past and as they did recently with the fix of the bugs of the task manager.

I ran into this strange issue the other day - I extract from com0presed files a lot. I was copying over some files from a zip for a program update and it took me a bit to figure it out - it silently failed. I ended up deleting the originals. before copying.

This release is a bit of a muck-up, isn't it?