185 replies to this topic

[HavoX]

Even though Win10 was just released a couple weeks ago, that won't stop Microsoft from delivering Preview Builds. One thing that caught my attention was this:

 

One of those improvements is a new concept called a compression store, which is an in-memory collection of compressed pages. This allows the Memory Manager to compress unused pages instead of writing them to disk when the need arises. According to Microsoft, this will result in better responsiveness across all of Windows 10.

 

 

[DCEnygma]

Having now moved both of my desktops to Windows 10 I have to say I'm quite impressed with the performance of both machines. Both seem to be responding faster overall in terms of application launching and OS startup/shutdown. I also haven't yet encountered any incompatibilities between software I was using, so that's good. I ended up doing full reformats for both, but they were both also briefly upgraded before the reformat and there is a noticeable difference between the two, so I'd have to recommend a clean install if possible. That said, you can do the reformat from within Windows without need for boot media after upgrading to 10, so that's pretty nice.

 

I also tested out the Xbox One streaming and it is pretty sweet. On top of that, my brother in law was able to use his Xbox One as a pseudo-capture card for his Wii U to stream, which is kinda neat.

 

So yeah, pretty happy so far!

[TheLegend_njf]

I'd say I'm not fully with you DCE.

 

 

A process named Runtime Broker seems to put a damper on my satisfaction of this update. Considering this process has been troubling people since Windows 8, and the purpose of Windows 10 is to solve the problems that Windows 8 has created. It doesn't seem good that I have such a process running on my new computer with a fresh new windows install.

 

This process uses 25% of my 6 core 3.5 Ghz CPU on average!! I've read online that this process has caused many lower end pcs to simply crash and just can't keep up with the demands.

 

There isn't much reliable information online how to stop it either. Microsoft says it this process is using an unnaturally high amount of cpu and/or ram, then it is an issue with an app, and they take no responsibility. But Damn, I only just installed this thing. I don't think I even have any apps on it, I never been to the app store I don't think. 

[Kite]

I'd say I'm not fully with you DCE.

 

 

A process named Runtime Broker seems to put a damper on my satisfaction of this update. Considering this process has been troubling people since Windows 8, and the purpose of Windows 10 is to solve the problems that Windows 8 has created. It doesn't seem good that I have such a process running on my new computer with a fresh new windows install.

 

I didn't have any problems with it, but I did run into a reddit post yesterday about someone having a similar problem. I think they fixed it by going to Settings->System->Notifications & Actions and switching off Show me tips about Windows. Not sure if that will help or not.

 

Only other ideas I have are to check Settings->System->Apps & Features for things you don't want or check Settings->Privacy->Background Apps for apps you don't want running in the background.

[TheLegend_njf]

I didn't have any problems with it, but I did run into a reddit post yesterday about someone having a similar problem. I think they fixed it by going to Settings->System->Notifications & Actions and switching off Show me tips about Windows. Not sure if that will help or not.

 

Only other ideas I have are to check Settings->System->Apps & Features for things you don't want or check Settings->Privacy->Background Apps for apps you don't want running in the background.

 

Neither options worked for me, as you can see, I've tried a few things.

 

I just done a Windows Update. I heard simply updating Windows has worked for some people. Lets hope this works for me. 

[Nicholas Steel]

Neither options worked for me, as you can see, I've tried a few things.

 

I just done a Windows Update. I heard simply updating Windows has worked for some people. Lets hope this works for me. 

If you upgraded to Windows 10 and didn't do a clean install, open an elevated Command Prompt window (Right-Click it, Run it as an administrator) and type the following:

 

sfc /scannow

 

Leave the computer while this process is operating and it will try to fix any corrupt Windows system files. If it says it couldn't fix things, repeat the process in Safe Mode with Command Prompt access. If it still isn't able to fix things, compress and upload the CBS log files located at C:\Windows\Logs\CBS somewhere and I'll see if the files that are corrupt are even potentially responsible for your issue.

 

You could also post a report (With a link to the files) on the relevant Technet forum as there's people that are more likely to be able to understand it better than me, there. Windows 10 Technet forum: https://social.techn...rt=lastpostdesc

Edited by Nicholas Steel, 20 August 2015 - 01:34 AM.

[Ben]

Runtime Broker is a process that handles permissions and things like tile updates for Metro/Universal apps. If you have a third-party app with a memory leak it will cause Runtime Broker to go nuts, and you would have to uninstall that app to solve the problem usually. Basically those third-party apps are using a deprecated method to update their Live Tile in the start menu and causes it to chew through

 

NJF, I found this solution. Fire up regedit.exe and change this entry:

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker]

 

"Start" dword:00000003 

Change the 3 to 4.

 

Changing the value to 4 sets the service to disabled (3 is manual startup, which only runs when you run a Metro/Universal app, 2 makes it start automatically with Windows. Don't set it to 1.) Then kill the process if it is still running.

 

However this will stop any apps from the Microsoft Store from running.

[DCEnygma]

However this will stop any apps from the Microsoft Store from running.

 

...not sure that cutting off an entire section of functionality of Windows is a "solution."

 

Unfortunately this goes back to what I was saying about upgrades vs reformatting. I did indeed see a difference in performance. If you have the ability, maybe a good option to back up your files you want to keep, then tell Windows to Reset, which will completely reformat.

[TheLegend_njf]

DCE's response is why I didn't take that suggestion when I read it up online. Like I said, I did my research.

I also have a thing against editing the registry. It is my belief that people should stay out of the registry, but that's just a personal opinion.

Either way, ever since I downloaded and installed the update yesterday, the problem seems to have gone away. I'll be keeping an eye on my cpu usage throughout the day to confirm this.

[TheLegend_njf]

So now that it's been almost a full day since I downloaded a Windows update, I can confirm that my issue with Runtime Broker has been resolved, and I can finally start enjoying my Windows 10.

[Magi_Hero]

I just installed Enterprise on a secondary work laptop that was failing during beta. I'm looking to see if the driver compatibility has been resolved. So far many of the Lenovo drivers have been working fine. I'll stress test it a little tomorrow.

[Demonlink]

I just installed Enterprise on a secondary work laptop that was failing during beta. I'm looking to see if the driver compatibility has been resolved. So far many of the Lenovo drivers have been working fine. I'll stress test it a little tomorrow.

From Lenovo user to Lenovo User, if your PC isn't that old unlike mine (2011 I think?), most drivers should work. If it is a bit old, do not update them.

Edited by Demonlink, 20 August 2015 - 08:15 PM.

[Valientlink]

So I tried the windows 10 upgrade, and I have some comments.

 

It is absolutely terrible (imo). if you are a 7, 8, or 8.1 user, I would highly advise against downloading this upgrade. Numerous complications arose from installing the upgrade. For one, my laptop brightness was fixed on high (higher than normal, and it gave me headaches). I tried everything there is to try from 3rd party programs to restartting to even messing with the boot settings but nothing fixed it. On top of this, it took 10 minutes to boot up, ran very, very slowly, and the graphics card drivers did not seem to install correctly, resulting in very poor graphical capabilities (project 64 was averaging around 40 fps).

Not to mention, constant stupid pop-up windows, hibernate being hidden, and if you were using classic shell 8 you won't like windows 10 start menu very much. I thought windows 10 was pure shit, and quickly downgraded back to 8.1 and it was a breath of fresh air. Some might not have problems with win10, but just know many (including me) do.

 

Oh yeah, if you aren't running on 8.1 it will wipe out all your files I think, so keep that in mind.

 

What's funny is that I didn't like 8.1 that much, but as soon as I installed windows 10 I immediately realizied how not bad 8.1 really is.

Edited by Valientlink, 22 August 2015 - 04:23 AM.

[HavoX]

So I tried the windows 10 upgrade, and I have some comments.

 

It is absolutely terrible (imo). if you are a 7, 8, or 8.1 user, I would highly advise against downloading this upgrade. Numerous complications arose from installing the upgrade. For one, my laptop brightness was fixed on high (higher than normal, and it gave me headaches). I tried everything there is to try from 3rd party programs to restartting to even messing with the boot settings but nothing fixed it. On top of this, it took 10 minutes to boot up, ran very, very slowly, and the graphics card drivers did not seem to install correctly, resulting in very poor graphical capabilities (project 64 was averaging around 40 fps).

I've read that a clean install is recommended over upgrading from 7/8/8.1. You should have thought about that sooner.

 

What's funny is that I didn't like 8.1 that much, but as soon as I installed windows 10 I immediately realizied how not bad 8.1 really is.

The thing is 8.1 has matured a lot since its release, but Win10 is still a baby... you should give it some time before it matures.

[Kite]

So I tried the windows 10 upgrade, and I have some comments.

 

It is absolutely terrible (imo). if you are a 7, 8, or 8.1 user, I would highly advise against downloading this upgrade. Numerous complications arose from installing the upgrade. For one, my laptop brightness was fixed on high (higher than normal, and it gave me headaches). I tried everything there is to try from 3rd party programs to restartting to even messing with the boot settings but nothing fixed it. On top of this, it took 10 minutes to boot up, ran very, very slowly, and the graphics card drivers did not seem to install correctly, resulting in very poor graphical capabilities (project 64 was averaging around 40 fps).

 

It's unfortunate that you had a bad experience with installing Windows 10. There is still a lot of hardware that hasn't had updated drivers for the OS and there is admittedly some driver baffonary happening on Windows Update for some people since the Windows Update drivers are older than the manufacturer drivers or incompatible with the hardware in some cases. It sounds like your laptop brightness and video problems were driver related. The startup being so slow is probably another conflict happening somewhere. While there have been a lot of success stories, stuff like this does actually happen. So yeah, I don't blame you for rolling back to Windows 8.1. I probably would have also in that case since there's only so much driver juggling I'm willing to do, especially for major devices like the video.

 

But I'll go through some of your points here since I don't think everything you said is accurate.

 

constant stupid pop-up windows

 

You can disable almost all of those if they bother you.

 

hibernate being hidden

 

Hibernate is hidden, but I think you can make it show up: http://winaero.com/b...-in-windows-10/

 

They probably did this because they are trying to promote the fast startup a bit more and maybe feel users manually initiating hibernation is rare thanks to that. Fast startup is a pseudo hibernation since it also keeps files on the hard drive about the state of the OS to make starting up faster. It's kinda silly that full blown hibernation would be hidden for a laptop though.

 

if you were using classic shell 8 you won't like windows 10 start menu very much

 

Classic Shell works in Windows 10. I dunno if you were implying it didn't work or if you were just saying that if people felt to need to use it in 8 they wouldn't like 10, but figured I'd mention it.

 

Oh yeah, if you aren't running on 8.1 it will wipe out all your files I think, so keep that in mind.

 

I did an upgrade from Windows 7 to Windows 10 and all of my files, programs, settings for those programs, and most of my explorer settings (the ones that were still in Windows 10) were kept. It even kept my shell extensions for explorer like Link Shell Extension when I thought it was going to wipe them. About the only thing that wasn't kept was that it switched my UAC back to full annoying popup that freezes screen interaction mode and I had to turn it down since I've got some programs that would have been really annoying to use otherwise. My Windows 7 install was still pretty recent, so I didn't even bother to do a clean reset afterwards and things have been working pretty smoothly for me.

 

So yeah. Again, it's pretty understandable that you went back to Windows 8.1. There's still a lot of devices that just haven't gotten driver updates to work smoothly in Windows 10. This early on, you'd probably have to do some hunting to find compatible drivers depending on your laptop. It might be worth giving it a shot again a few months from now to see if Windows or your laptop manufacturer have gotten their drivers together. Or if you're happy with 8.1, that's fine too.