Micro$oft up to its old tricks again...

[wombat666]

One of the handy little options in GWX is the 'Clear Windows Update Cache'.
Out-bloody-standing!

I cleared it last Monday and it removed a triple digit number of 'hidden updates' plus any trace of W10 'invitations', ran it a few minutes ago and it nuked another 32 updates!
I'll still check but I'll do it my way.
And a reminder please team, we do NOT discuss anything resembling politics in ANY forum on this site.

[gman5250]

One of the handy little options in GWX is the 'Clear Windows Update Cache'.
Out-bloody-standing!

I cleared it last Monday and it removed a triple digit number of 'hidden updates' plus any trace of W10 'invitations', ran it a few minutes ago and it nuked another 32 updates!
I'll still check but I'll do it my way.
And a reminder please team, we do NOT discuss anything resembling politics in ANY forum on this site.

I downloaded and ran the GWX...cleared 37 from the Update Cache.


BTW...
If any one here posts up a fix for the frigging' tool tip balloon in Win10...I'd be extremely grateful. I have coded the darned thing out ten ways to Sunday, but I still get the ridiculous little sucker every time I roll over anything.

Using the mouse some balloons have been suppressed, but with the Wacom Pen and Tablet..no joy, always a balloon.

Worst part is in the SDK annotator. Imagine placing every tree and house in a small city one little square at a time...when I go to draw the square, bingo up pops the balloon right on top of the space I want to draw. It is absolutely maddening...

At one point I had fixed it...but when Win10 updates, it comes right back.

[TuFun]

Going to be interesting to what Redstone 1 update will bring to Win 10. Something like 1200 changes.

[KellyB]

Going to be interesting to what Redstone 1 update will bring to Win 10. Something like 1200 changes.

An interesting choice of name for it.

[AckAck]

An interesting choice of name for it.

They didn't ALL blow up...

[KellyB]

They didn't ALL blow up...

But when they did, it was spectacular!

[TuFun]

I was listening on the radio a discussion of Windows 10 by Lauren Weinstein and a lady called in stating that Win 10 was trying to install on her computer. Like others she rejected the process, but found it was installing anyways. The attempted install failed... not enough memory!

[Blackbird686]

It would seem to me that clicking "no" to an update notice of any kind, from anyone on YOUR personal computer, should be the end of it. Having Windows 10 begin to download and install on your machine after you specifically click "no" because you choose not to have it, or as one gentleman stated in an earlier post.. some of his software won't run under Windows 10, to me is the same as being forced to agree to something without being allowed to read the contract. Not sure if there is any legal implications involved here but "agreeing" to an action, such as allowing Microsoft to install Windows 10 by clicking "no" or closing the update window altogether doesn't seem to be on the level...in any case. I don't like the method MS is using to foist Windows 10 on to my machine... it won't handle it. Windows 10 may be just fine on a different machine that was designed to handle it's requirements.

It's like going to the hospital to have a medical procedure done, and agreeing to what the doctors are going to do to you, without them telling you about what's what. Just my 2 bits....

BB686

[Allen]

Call your lawyers boys and girls....

http://www.computerworld.com/article...0-upgrade.html

[n4gix]

Yea! I read that yesterday in RadioReference.com and was just fixing to pass it along here.

[Naismith]

In a moment of madness (I blame Jack Daniels for my poor judgement) on Saturday I thought "oh what the hell" and let W10 install. It all went flawlessly in about 25 minutes. Then I fired up FSX..... Uh oh, that took 3 minutes boot up. The the aircraft selection screen took about 40 seconds to open up. 3 minutes select and run a flight. Then the actual sim, well that was like a kinetoscope. I even deleted the fsx.cfg to see if that was the problem. It wasn't. By evening time I was back in W7. That went pretty seamlessly and in less than 10 minutes.