Windows 10 Insider Preview Dev Build 20246.1 (fe_release) - Oct. 29 Insider

i put back my setting to 3840 x 2160...hope another new build not change it

carpangler1 said:

This can be fixed by disabling all the hyper v stuff in optional features. Took me a while to sort it though. I'll post a vmware link on it tomorrow night if you are stuck.

I do not want to disable Hyper-V. VMWare 16 does support Hyper-V and I've been using them together for sometime now. Only in the last two updates it stopped working.

I agree but until its fixed by Microsoft or vmware then not a lot can be done. Hopefully next build.

Except for a couple of minor issues I find this build to be running great.

Wannagofast said:

These Fast (Dev) ring releases seem to me to be progressively becoming worse each week.

Broken basic functions with the task bar and start menu, and programs hanging on every shutdown.
GSOD's over and over on a machine that is, and has been perfectly stable with all other version installs.

I used to look forward to trying out the latest and greatest each week. Most often they were perfectly usable.
Now I wait until Saturday to try them, knowing I will probably have to just image it back after a short trial run.

Hopefully they will get their act together in the future where I will actually be able to test them again.

peace
wanna

I'm seeing the same. Numerous programs/features top working. Integration with VMware is getting worse. I used to use the latest builds on my main machine (and looked forward to it) and that was fine for years. Now I daren't as too much critical stuff gets broke, so it's a secondary machine only. I know it's builds for testing but they are getting to the point where it's very hard. I can live with minor issues but major issues I can't. As you say they need to get there act together. I'm not sure how much notice they take of the Feedback Hub either.

bncz135 said:

Anyone notice any NTFS warnings in the event log for this build or the previous one (20241) ??

Event id 7 "NTFS has detected torn write on a volume"

Chkdsk showed no problems. Disk is a Samsung 970 NVMe.
I found 2 other records in Feedback with the same issue for this build.

Yep suddenly have this

Ntfs has detected torn write on a volume.

Volume correlation Id: {f2307ef7-afc8-4260-b942-58317141a793}
Volume name: C:
Volume label: OS
File reference: 0x550A
File name: \Windows\System32\wbem\en-US
Byte offset of the buffer within the file: 4096
Byte offset of the torn structure within the buffer: 16384
Block index: 0
Expected sequence number: 28
Actual sequence number: 0

RussellW said:

Yep suddenly have this

Ntfs has detected torn write on a volume.

Volume correlation Id: {f2307ef7-afc8-4260-b942-58317141a793}
Volume name: C:
Volume label: OS
File reference: 0x550A
File name: \Windows\System32\wbem\en-US
Byte offset of the buffer within the file: 4096
Byte offset of the torn structure within the buffer: 16384
Block index: 0
Expected sequence number: 28
Actual sequence number: 0

This definitely started on build 20241 for me. Scanning feedback for "torn write" shows several other users with the same problem including those who ended up with a non bootable system.

I see it too. I also see around ten more all in the System32 folder of windows.


Ntfs has detected torn write on a volume.

Volume correlation Id: {214e7a4d-afaf-4b55-b5a5-7d213fd6272b}
Volume name: C:
Volume label:
File reference: 0xE72
File name: \Users\noahw\AppData\Local\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\LocalState\AppIconCache\1 00
Byte offset of the buffer within the file: 0
Byte offset of the torn structure within the buffer: 24576
Block index: 0
Expected sequence number: 3
Actual sequence number: 35