Windows 10TP build 10074 impressions..

For me, this build is a big step backwards. Ever since installing this build, I am back to getting the filesystem corruptions that haven't happened for several builds now. And, clean installs do NOT fix this, at least, not this time.

Also VERY disappointed to read that the Start Menu is all but finished in its current state. By their own reports, Stardock made over $150 Million (!) dollars from Start8 (30 million downloads at $5 each). You would think with that amount of revenue, MS would be interested in producing something that effectively competes -- but this miniature Start Screen doesn't meet the needs of either "camp". The touch-screen folks don't need it because they have the Start Screen; the desktop folks don't want it because it's a scaled-down version of the Start Screen, NOT a Win7-style Start Menu. And ... Stardock already has a beta version of Start10 out. So, at least, there is a "solution" to the Start Menu problem that MS clearly is not interested in solving.

silv55 said:

Also after i do this workaround settings;

Go to run and type gpedit.msc
click on Computer Configuration
click on Administrative templates
click on System
click on Device Installation
click on Device Installation Restrictions
Enabled Prevent Installation of Devices not described by other policy settings
Uninstalled driver ticked delete driver.
Also go to Uninstall program to remove Synaptic software.
Reboot
Disable or Unconfigure Device Installation Restrictions
And install Synaptics driver ver 16.2

i get this;see pic;

http://postimg.org/image/4s0dmpl35/b496d97d/

Yes, it's not installing the new drivers you don't want. This is the situation you want. Why are you trying to "fix" it?

Kari said:

Testing various image customization scenarios I happened to get this:

I like it when an error dialog is clear and easy to understand, showing exactly what the error was :).

I've seen this before.

I think when I got it (not with the latest build or latest ADK though) it was with an install set I'd created from the ICD.

I don't have my notes to hand, but seem to remember the problem was either:

1. The installer didn't seem able to partition the disk on its own. Starting with a partitioned disk got past the error, although obviously this is cheating; or
2. The Name and Description in the WIM file I'd created weren't right. In the earlier version I had to call it Windows 8 (can't remember the exact wording) as per the WIM in the original ISO, to get past an error.

Although of course, given the wonderfully specific error message, it could be something else entirely...

Hi All,
Build 10074 still seems rather buggy to me, as I stated in my original post in here, in addition..windows defender won't update properly, I keep receiving an error message. So for now, I have returned to using windows 8.1, which is a LOT more stable than windows 10.
David

You know what is really sad, I read about all these problems, and it makes me sad because I just for some reason don't get them. . .not sure if that is a good thing or bad. Maybe I will get them, but all at the same time. . .oh, oh. . .

Lee said:

You know what is really sad, I read about all these problems, and it makes me sad because I just for some reason don't get them. . .not sure if that is a good thing or bad. Maybe I will get them, but all at the same time. . .oh, oh. . .

Mine does not seem buggy but I do get the forced windows updates. Apparently we are not allowed to turn them during the preview. I installed updated display drivers but win 10 uninstalled them and the windows update installed it's own. They still work fine but I didn't get a choice. Windows Defender updates fine for me also.