So how are you liking Win10 so far?

[Ketchup]

The recovery option takes up a good bit of space when updating builds. And of course the more you "update" the builds, the fatter the partition will get. So every once in a while you may need to try the shrink option, nuke it for a clean install, or make another drive and clone it.

 

[Makaveli]

Another option also before even looking at resizing partitions and nuking etc is disk clean up.

Go into it and select clean up system files.

This was what mine looked like after updating to build 10074 in my VM.

Also check for restore points.

Sometimes this alone will allow you to free up enough space.

 

[Ketchup]

Another option also before even looking at resizing partitions and nuking etc is disk clean up.

Go into it and select clean up system files.

This was what mine looked like after updating to build 10074 in my VM.

Also check for restore points.

Sometimes this alone will allow you to free up enough space.

Good suggestions. Just remember that this will only free "virtual" space, not the size of the vmdk file.

 

[DrMrLordX]

That is more than enough space my original partition was 20GB and I had to increase it to 25GB because the previous installed left so much data behind it was taking up space.

Are you getting any error codes with the issues you are having?

Yeah, I posted them above to RampantAndroid, though those only applied to the 10061 update. Now that I've finished pulling down the 10074 iso, it's trying to feed me 10074 through Windows Update. Blah! I'll just upgrade from the iso . . . later.

Another option also before even looking at resizing partitions and nuking etc is disk clean up.

Go into it and select clean up system files.

Sometimes this alone will allow you to free up enough space.

Yeah, did that. That's why I have 80Gb free now (used to be less).

 

[FrankRamiro]

Hi guys;I upgraded to Win 10 Tp build 10074 i had problems because this build came with touch-pad drivers by default,my HP Dv 5,6 have no touch-pad can i uninstall ''Synaptic pointing drivers''? are these drivers are for the touch-pad?,

 

[FrankRamiro]

Yeah, I posted them above to RampantAndroid, though those only applied to the 10061 update. Now that I've finished pulling down the 10074 iso, it's trying to feed me 10074 through Windows Update. Blah! I'll just upgrade from the iso . . . later.



Yeah, did that. That's why I have 80Gb free now (used to be less).

the latest builds 10061 -10074 all suck no good,they will not update or not running at all and go back to previous build 10049 which is running fairly good,
it seems to win 10 Preview is getting worse instead of getting better as next builds are presented,i don't think testers will put up with win 10 bullshit,what a crappy OPS they building, i think i go back to Win 7 or Linux.

 

[DrMrLordX]

the latest builds 10061 -10074 all suck no good,they will not update or not running at all and go back to previous build 10049 which is running fairly good,
it seems to win 10 Preview is getting worse instead of getting better as next builds are presented,i don't think testers will put up with win 10 bullshit,what a crappy OPS they building, i think i go back to Win 7 or Linux.

Most of what I've heard about 10074 has been positive from those that can actually get it running. It may not be accurate to assume that the update/upgrade headaches are solely the fault of the new build. Cruft from old builds - corrupt/faulty Windows Update caches, funky drivers, etc - may be making it increasingly difficult to keep these Win10 installs running that have been in the upgrade cycle for months.

For my part, I tried an in-place installation from the 10074 iso. The first one failed, though this time it got all the way through the second stage of the updater before rebooting, only to boot to a black screen (monitor had a signal, it was just . . . black). I have Win10 set up to give me a bootloader, so when I manually restarted the machine after the failed upgrade, it gave me three boot options:

Windows preview
Setup
Windows preview

So I picked Setup, and it rolled me back to 10049. Then it told me I had some problem with a MIGRATE operation (all caps, I don't have the exact error message in front of me). I did look up the message, and it appears to be related to a driver problem.

So I tried again, same problem, black screen in the third part of the installation/upgrade process. This time, I selected the first Windows preview option in the bootloader, and . . . success! 10074 finished installation. Immediately after I booted into Win10 for the first time, AMD QuickStream popped up like it always does and informed me that it needed to be reinstalled, so I did, and then rebooted, and . . . now it won't boot except in safe mode. Trying sfc /scannow (which mercifully will run this time, up yours Windows Resource Protection! I win this round!).

It may be that Catalyst 15.2 from 4/1 is the reason why all those updates to 10061 and 10074 failed in the first place.

edit: Yup, it was the latest 15.2 driver. Uninstalling 15.2 AND QuickStream got 10074 to boot. It works. Now I just have to find a suitable video driver . . . I may re-try 15.2 without QuickStream to see if I can get that to work, since Windows Update is going to shove that driver down my throat constantly if I don't. Grr!

One of these days, MS is going to have to give us back configurable updates . . .

edit edit: Okay, 15.2 w/out QuickStream appears to work. For now. And all the desktop resolution problems I had with the 4/1 revision of 15.2 are gone, too, which is . . . interesting to say the least.

 

[Jackalito]

Most of what I've heard about 10074 has been positive from those that can actually get it running. It may not be accurate to assume that the update/upgrade headaches are solely the fault of the new build. Cruft from old builds - corrupt/faulty Windows Update caches, funky drivers, etc - may be making it increasingly difficult to keep these Win10 installs running that have been in the upgrade cycle for months.

For my part, I tried an in-place installation from the 10074 iso. The first one failed, though this time it got all the way through the second stage of the updater before rebooting, only to boot to a black screen (monitor had a signal, it was just . . . black). I have Win10 set up to give me a bootloader, so when I manually restarted the machine after the failed upgrade, it gave me three boot options:

Windows preview
Setup
Windows preview

So I picked Setup, and it rolled me back to 10049. Then it told me I had some problem with a MIGRATE operation (all caps, I don't have the exact error message in front of me). I did look up the message, and it appears to be related to a driver problem.

So I tried again, same problem, black screen in the third part of the installation/upgrade process. This time, I selected the first Windows preview option in the bootloader, and . . . success! 10074 finished installation. Immediately after I booted into Win10 for the first time, AMD QuickStream popped up like it always does and informed me that it needed to be reinstalled, so I did, and then rebooted, and . . . now it won't boot except in safe mode. Trying sfc /scannow (which mercifully will run this time, up yours Windows Resource Protection! I win this round!).

It may be that Catalyst 15.2 from 4/1 is the reason why all those updates to 10061 and 10074 failed in the first place.

edit: Yup, it was the latest 15.2 driver. Uninstalling 15.2 AND QuickStream got 10074 to boot. It works. Now I just have to find a suitable video driver . . . I may re-try 15.2 without QuickStream to see if I can get that to work, since Windows Update is going to shove that driver down my throat constantly if I don't. Grr!

One of these days, MS is going to have to give us back configurable updates . . .

edit edit: Okay, 15.2 w/out QuickStream appears to work. For now. And all the desktop resolution problems I had with the 4/1 revision of 15.2 are gone, too, which is . . . interesting to say the least.

First of all, sorry because I'm using Tapatalk and I can't see your specs. What graphics card do you have? Mine is an R9 290X and I can confirm multiple issues with the latest drivers from April 1st on my end as well. And not only in build 10074, but all the way back to 10056.

So, I've been in touch with AMD to report my issues and see if they can replicate them and come up with an updated driver.

Now I'm using the previous drivers for Windows 10 of March 11, and so far so good. In order to prevent Windows Update from overriding my drivers with the problematic ones, I've used a script I was told about on the official Insider forums: https://answers.microsoft.com/en-us...ver-from/bff07224-4ce2-4b42-ab29-68c3a305d730
Following those instructions, I can keep on using Windows Update and the problematic drivers are not shown anymore.

If you want to read about the problems I was experiencing, you can do so here: https://answers.microsoft.com/en-us...-lastest/6f9fdb7b-2c6a-4630-89d3-b143f1f5f117

Cheers!

 

[razel]

Hi guys;I upgraded to Win 10 Tp build 10074 i had problems because this build came with touch-pad drivers by default,my HP Dv 5,6 have no touch-pad can i uninstall ''Synaptic pointing drivers''? are these drivers are for the touch-pad?,

Yes, refer to my #666 post. You're lucky you're not getting a blue screen. The Synaptics drivers are a mess. It's be fine if MS allowed us to manually check for updates or even exclude certain ones, but oh well. Oh well.

 

[DrMrLordX]

First of all, sorry because I'm using Tapatalk and I can't see your specs. What graphics card do you have?

I have an A10-7700k. I'm using the iGPU (Spectre).

Mine is an R9 290X and I can confirm multiple issues with the latest drivers from April 1st on my end as well. And not only in build 10074, but all the way back to 10056.

So, I've been in touch with AMD to report my issues and see if they can replicate them and come up with an updated driver.

Now I'm using the previous drivers for Windows 10 of March 11, and so far so good. In order to prevent Windows Update from overriding my drivers with the problematic ones, I've used a script I was told about on the official Insider forums: https://answers.microsoft.com/en-us...ver-from/bff07224-4ce2-4b42-ab29-68c3a305d730
Following those instructions, I can keep on using Windows Update and the problematic drivers are not shown anymore.

If you want to read about the problems I was experiencing, you can do so here: https://answers.microsoft.com/en-us...-lastest/6f9fdb7b-2c6a-4630-89d3-b143f1f5f117

Cheers!

I read your post in the above-linked thread, and I can confirm the slowdowns, though I did not immediately link them to the driver (I figured it was just . . . something else, wasn't sure what). In addition to the problems you've had, I had a problem where my monitor (ancient Gateway FPD1730 17" LCD monitor) would have disagreements with the OS about the current resolution if I chose the max resolution for the monitor (1280x1024). The OS thought it was setting 1280x1024 on the desktop, but the monitor detected 1024x768, so I wound up with a desktop display "squished" into a little black box on the screen. It was weird. That isn't happening anymore in 10074 (same driver).

I may still be having the slow boot + slow reset/shutdown problems, but I haven't done a lot of work in 10074 so it's hard to say.

On top of all that, the version of AMD QuickStream that ships with the 4/1 driver seems to prevent 10074 from booting at all. Have you tried using the 4/1 driver w/out QuickStream? Maybe that would resolve some of your trouble?

Yes, refer to my #666 post. You're lucky you're not getting a blue screen. The Synaptics drivers are a mess. It's be fine if MS allowed us to manually check for updates or even exclude certain ones, but oh well. Oh well.

Post #666? No wonder you're having problems . . .

*cough*

 

[HeXen]

Did anyone test game performance with the latest builds? That's all I care about

 

[FrankRamiro]

Thanks,well i finely decided to make an ISO of Win 10 TP build 10074 and clean install rather then update and all good for now.

 

[Jackalito]

I have an A10-7700k. I'm using the iGPU (Spectre).



I read your post in the above-linked thread, and I can confirm the slowdowns, though I did not immediately link them to the driver (I figured it was just . . . something else, wasn't sure what). In addition to the problems you've had, I had a problem where my monitor (ancient Gateway FPD1730 17" LCD monitor) would have disagreements with the OS about the current resolution if I chose the max resolution for the monitor (1280x1024). The OS thought it was setting 1280x1024 on the desktop, but the monitor detected 1024x768, so I wound up with a desktop display "squished" into a little black box on the screen. It was weird. That isn't happening anymore in 10074 (same driver).

I may still be having the slow boot + slow reset/shutdown problems, but I haven't done a lot of work in 10074 so it's hard to say.

On top of all that, the version of AMD QuickStream that ships with the 4/1 driver seems to prevent 10074 from booting at all. Have you tried using the 4/1 driver w/out QuickStream? Maybe that would resolve some of your trouble?



Post #666? No wonder you're having problems . . .

*cough*

Sorry, but could you please explain to me what QuickStream is? I've never heard of it.
Oh, with the previous Windows 10 drivers I'm using I have issues while playing Mortal Kombat X, so back to Windows 8.1 to minimise issues.

 

[ArisVer]

Would you recommend a newbie (me) on the technical previews to go on for fast builds?

 

[DrMrLordX]

Sorry, but could you please explain to me what QuickStream is? I've never heard of it.
Oh, with the previous Windows 10 drivers I'm using I have issues while playing Mortal Kombat X, so back to Windows 8.1 to minimise issues.

Quickstream:

http://support.amd.com/en-us/kb-articles/Pages/AMDQuickStreamTechnology.aspx

That says it better than I can, but I'll be buggered if it ever made a positive difference. I can live without it.

Would you recommend a newbie (me) on the technical previews to go on for fast builds?

I don't know that I'd recommend any of the preview builds for anything other than curiosity. 10074 seems to work okay, so far . . .

 

[Jackalito]

Quickstream:

http://support.amd.com/en-us/kb-articles/Pages/AMDQuickStreamTechnology.aspx

That says it better than I can, but I'll be buggered if it ever made a positive difference. I can live without it.



I don't know that I'd recommend any of the preview builds for anything other than curiosity. 10074 seems to work okay, so far . . .

Thanks for the link. My PC is a desktop with a dedicated R9 290X, so it's not compatible with such technology.

 

[FrankRamiro]

Yes, refer to my #666 post. You're lucky you're not getting a blue screen. The Synaptics drivers are a mess. It's be fine if MS allowed us to manually check for updates or even exclude certain ones, but oh well. Oh well.

But i do some times after reboot just after it installs updates,right now i have this Synaptics driver update for Synaptics SMBus TouchPad - Error 0x80070002

and it just freezed and gave me the error dpc watchdog violation, and rebooted,this a mess what the hell this win 10 tp is doing this is unaceptable

 

[RampantAndroid]

But i do some times after reboot just after it installs updates,right now i have this Synaptics driver update for Synaptics SMBus TouchPad - Error 0x80070002

and it just freezed and gave me the error dpc watchdog violation, and rebooted,this a mess what the hell this win 10 tp is doing this is unaceptable

It's tech preview for a reason 😉

Drivers are probably not going to be stable until it has been released and maybe + some time.

 

[escrow4]

I've been running 8 (and 8.1) since Day 1, and I don't know if its OS updates or drivers, but Win 8 Day 1 or 2 release in 2012 felt rough. Not Metro, the OS. Worked fine, but it wasn't mature. To me at least.

 

[FrankRamiro]

It's tech preview for a reason 😉

Drivers are probably not going to be stable until it has been released and maybe + some time.

thanks i know, i found this info,don't know it this works in win 10 tp,please advice.



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

 

[razel]

Here's another way to stop specific drivers using PowerShell:

Install Windows Update Powershell Module

Get-ExecutionPolicy <Make note of your current policy>
Set-ExecutionPolicy -ExecutionPolicy Unrestricted
Import-Module PSWindowsUpdate
Set-ExecutionPolicy -ExecutionPolicy Unrestricted <Set policy back to original>

Get-WUList
Hide-WUUpdate -Title "Synaptics driver*"

Works wonderfully... c'mon MS... let's get that checkbox back in Windows Update... so easy.

 

[RampantAndroid]

Here's another way to stop specific drivers using PowerShell:

Get-WUList
Hide-WUUpdate -Title "Synaptics driver*"

Works wonderfully... c'mon MS... let's get that checkbox back in Windows Update... so easy.

Let's get the ability to select updates back in general. Forced updating is not OK.

 

[amittalkin]

Well, I hate those icons, in addition I want to see some improvements regarding network settings, like detailed network adapter info and direct access to network adapter settings from network tray icon.
And some kinda info in tray for network traffic like netspeedmonitor does.

 

[ArisVer]

Let's get the ability to select updates back in general. Forced updating is not OK.

Totally true. But I see manual updates go the route of the Control Panel.


Edit. I believe the icons will be fixed by the time they release Windows 10.
And something else. It looks like build 10074 (or 10079) is on the slow track now.

 

[RampantAndroid]

Totally true. But I see manual updates go the route of the Control Panel.


Edit. I believe the icons will be fixed by the time they release Windows 10.
And something else. It looks like build 10074 (or 10079) is on the slow track now.

The old windows update is gone from the CP. It's forced updates (or disabling wuauserv.)