Windows 10?

[m100]

thanks everyone. here's what i've done this morning on my old win7:

check for any installed updated listed above
found and removed some (not certain but i'm sure i remembered removing some of the same ones the other day)
rebooted
ran ccleaner
created a restore point
manually checked for windows updates

guess what 3083324 is there again as important and i've hidden it again. I could be wrong as i've said before my knowledge of computers in general is small but they seem to be hanging everything on that one update. it seems as if they are determined to get that through at all costs.

[Ernesto75]

When you look at this article

http://www.ghacks.net/2015/10/22/fir...arly-november/

you can tell that Windows 10 really is not mature.

MS released it much too soon.

And in this next patch you can see that MS continues to consider important to improve what almost everybody refuse to use.

[Leprechaun]

Originally Posted by JJ3027

My boot drives are external, I run a SATA cable from the motherboard out the back and have an external power adapter for the drive. All I do is swap the boot drives outside the box. It beats fiddlin' inside the PC every time I switch OS's.

I stored my drives inside the PC, but I removed the side parts of the case, so swapping isn't cumbersome too.

You could also use a hard disk mobile rack.

[JJ3027]

Originally Posted by Leprechaun

I stored my drives inside the PC, but I removed the side parts of the case, so swapping isn't cumbersome too.

You could also use a hard disk mobile rack.

Or an external dock, like Thermaltake's BlacX. You can connect via eSATA port on your PC (if you have one) for 3Gb or 6Gb speed. If not, then USB

[Ernesto75]

Susan Bradley is american and MVP Microsoft.
She is managing a petition which is directly sent to Satya Nadella, Microsoft leader.

Of course I signed it.

Here is the link :

https://www.change.org/p/satya-nadel...etition-letter

I hope many VEF members will sign it.

[Ernesto75]

Users of Chrome should worry.

Some hackers try to use Chrome by modifying it in order to make you believe you use Chrome.

https://blog.malwarebytes.org/online...-associations/

[Ernesto75]

REDMOND, Wash. — October 22, 2015 — Microsoft Corp. today announced the following results for the quarter ended September 30, 2015:
· Revenue was $20.4 billion GAAP, and $21.7 billion non-GAAP
· Operating income was $5.8 billion GAAP, and $7.1 billion non-GAAP
· Net income was $4.6 billion GAAP, and $5.4 billion non-GAAP
· Earnings per share was $0.57 GAAP, and $0.67 non-GAAP

And yet they also suppressed 7 800 jobs recently.

But this is only a beginning : there might be 1 000 more.

This tells why their CEO is placing such a great emphasis on Windows 10.

[Kimj]

Windows 10 is junk! I have gone back to MS DOS

[Rick Danger]

ZDNet.com

Dear Microsoft: Please stop breaking my perfectly good Windows 7
How can vendors expect to migrate reluctant users to more reliable and up-to-date operating systems like Windows 10 or El Capitan -- especially when upgrade notices and reminders break earlier versions?

By David Gewirtz for DIY-IT | October 26, 2015 -- 12:29 GMT (05:29 PDT) | Topic: Windows 10



Managing obsolescence is a huge challenge for platform vendors. There are usually two opposing forces driving the challenge: inertia and entropy. While both inertia and entropy can be described in some depth using actual science, for our purposes we'll summarize the terms in this way: people don't like to change and stuff breaks over time.

Take, for example, Windows XP. There is no doubt, from a technical and security point of view, that XP is long past its expiration date. It is actually dangerous to run on the Internet. But there are a whole lot of people who have been using XP forever, know it intimately, and don't want to give it up.

Then there are the systems built around XP. I had a content management system that ran on a development environment that would only run on 32-bit Windows XP. It took three years to move that beast away - three years of time-consuming and costly coding. There are machines and systems all over the world that would have to be substantially recoded and built - sometimes from scratch - to move off of XP.

There's also the cost. Sure, PCs are now dirt cheap. But a thousand dirt cheap PCs start getting really expensive. Many companies and individuals are loathe to spend the money to buy systems that replace perfectly good machines.

So despite all of Microsoft's efforts and all of our cajoling and warning, XP lives on.

While Windows XP is a no-brainer in the "must not use anymore" category, Windows 7 is a much more difficult challenge for Microsoft. Windows 7 is probably the most loved of Microsoft's modern operating systems: It was a clear home run, and -- due to Microsoft's incredible missteps with Windows 8 -- is the last truly trusted Microsoft operating system in many users minds.

For many users -- myself included -- there is no reason to upgrade existing machines to Windows 10. Windows 7 is perfectly functional, as safe as Windows machines are going to be, familiar, and rock solid.

And yet, overcoming upgrade inertia is not a Microsoft-only problem. I have a Mac mini running Mountain Lion (that's four revs back now in OS X land), but it's running my studio and I don't want to make changes until I can be sure everything will upgrade. Some of the specialty-video software I rely on doesn't support the more modern OS versions, so for now I'm leaving it un-upgraded.

This, of course, reinforces the system vendor's dilemma: supporting old systems is costly, regressive, and encourages users to run potentially unsafe gear. By contrast, getting users to upgrade keeps the flow of revenue going, while letting old systems gather moss doesn't do much for the bottom line.

Of course, it's in Microsoft's - and Apple's and Google's - best interests to encourage uptake of new OS releases. This isn't just about cash. After all, while all three companies need to continue to stoke the fires that drive their bottom lines, they're all very nicely profitable businesses with working business models.

They also need to drive OS upgrade uptake to keep their customers safe, to drive adoption of new gear, to keep the excitement level up, and to respond to all the opportunities created by the relentless pace of innovation across the industry.

The problem is, it's not a smooth path. Customers will be inconvenienced. There will be bugs. There will be profanity.

And goodwill will be lost

This weekend, Microsoft once again landed on my (insert profane term for excrement) list. About three and a half years ago, I bought a super high-end custom Sager 9150 laptop to serve as my primary work machine. At the time, it was about as RAM and SSD rich as possible, and it cost a mint. It was my main machine, and my main cycle-burners often require top-end power and their cost reflects that expense.

In any case, the Sager lasted about 15 months before I needed something even more powerful for my main work machine. But that didn't mean I retired the Sager. I just moved it off my desk area to run our big screen.

My house is also where my wife and I work, so we have a lot of systems set up to do double duty. While we have a big screen TV that can be used for Game of Thrones binge watching, it's tied to the Sager and is often used as a conference room white board, collaborative writing environment, and design space. I'm also sitting comfortably on the couch right now, using it to write this article.

We rely on that Sager. It runs Windows 7 and - until recently - has been rock-solid. That is, it was rock-solid until Microsoft started to harass us about upgrading the Sager to Windows 10.

Let's make this clear: it is not wise to upgrade this machine to Windows 10. It is a custom-built one-off machine with specially-tuned drivers. When I last contacted the folks at Sager about upgrading it, they started mumbling about inadvisability and you takes your chances. In other words, it's not supported.

My Sager 9150 was designed and lovingly optimized for Windows 7. No one knows what would happen if a Windows 10 upgrade were to be attempted, but everyone there generally shares the hair-on-the-back-of-the-neck feeling of it-would-be-ungood.

As I said back in July, I have no intention of upgrading the Sager to Windows 10. But Windows 7 on the Sager no longer agrees with that plan. A few months back, I started to get the GWXUX error shown at the top of this article. It means that the Get Windows 10 nag process is failing.

Since the message only showed up once every few weeks, I ignored it. But apparently, Microsoft really wants me to upgrade, because this weekend, the message has been showing up pretty much constantly.

Adrian Kingsley-Hughes wrote a piece just Friday about how to remove Windows nag prompts, but I'm annoyed because I don't want nag messages and I don't want to install a hack to avoid them. I'm not planning to upgrade because the manufacturer has stated it would be ill-advised.

I'm certainly not planning to upgrade when even the upgrade nag message can't seem to run without failing.

And yet, I expect I have many months (or even years) ahead of me, facing this sort of message, unless I take another probably inadvisable path of installing a piece of third party software to hack the GWXUX code to stop it from being annoying.

This is where I find myself at odds with Microsoft and disagreeing with its aggressive upgrade approach. It's important to get people off of Windows XP. But Windows 7 is (at least for now), just about as perfect an implementation of a Windows system as we're likely to see for the next decade.

It's perfect, of course, unless Microsoft goes out of its way to break it, in a misguided attempt to convince us all to move to its new version. But I'm telling you... breaking my computer is not going to inspire confidence, and it's not going to inspire me to upgrade to another Windows version.

The fact is, I'm now running a lot of Macs around Camp David, although many of them are running Windows 7 and Windows 8.1 in either Parallels and Boot Camp. If Microsoft breaks my existing machines, I'm now more likely to move to a Mac than another Windows machine. I'm also less and less likely to run Windows on those Macs, even in virtualized instances.

The only gotcha is that Apple, too, is nagging about OS upgrades. Apple wants me to upgrade to El Capitan, which some people report is solid, while others report it has bugs and more bugs.

That said, I would upgrade to El Capitan now, except for one small issue: Office 2016 breaks on El Capitan.

Yep, this whole article ends in an irony: Microsoft is pushing me to upgrade my Windows 7 machine, but because the upgrade nag is breaking, I'm not going to upgrade. And I'm not upgrading my Mac because... wait for it... Microsoft software can't handle the upgrade.

Inertia and entropy: Meet irony.

By the way, I'm doing more updates on Twitter and Facebook than ever before. Be sure to follow me on Twitter at @DavidGewirtz and on Facebook at Facebook.com/DavidGewirtz.

[Rick Danger]

Surprise, surprise. Microsoft's highly touted, "game changing" Surface Book was about as ready for prime time as Windows 10. But of course, Windows 10 is free whereas the Surface Book is premium hardware at a premium price.

I'm not really surprised. We saw at the beginning of the month when Windows 10 updates bricked existing Surface 3 tablets. What was Redmond's excuse? After all, it was Microsoft hardware, Microsoft firmware, Microsoft drivers, running Microsoft X "the best Windows ever". Duhhuhhh, not being able to get Windows X to bed down properly on your own products is not a powerful inducement for upgrading non-Microsoft products.

Yeah, I know. All new systems, esp. one's on the cutting edge have teething problems. I could just wish Microsoft would spend less on slick marketing campaigns and more on quality assurance.

ZDNet.com

Surface Book suffers from launch day bugs
Within hours of Microsoft's new Surface Book landing in the hands of customers I began seeing reports of serious bugs affecting Microsoft's new flagship device, the Surface Book.

By Adrian Kingsley-Hughes for Hardware 2.0 | October 27, 2015 -- 10:52 GMT (03:52 PDT) | Topic: Microsoft

Within hours of Microsoft's new Surface Book landing in the hands of customers I began seeing reports of serious bugs and issues affecting Microsoft's new flagship device.

While many are happy with their new purchase, there is no shortage of tales of woe. And the bugs are many and varied, and solutions for most of these - other than wait or send the machine back to Microsoft for replacement or refund - are thin on the ground.

Note that Microsoft doesn't seem to have set up an official support forum for the Surface Book as of yet, so many of these reports are coming via third-party sources.

Here are some of the issues affecting the Surface Book as reported by new owners:

Dead on arrival (or badly limping on arrival) Surface Books
Random crashes and lockups
Surface Book systems working fine until they're updated, following which they fail to load
Surface Book systems failing to boot when in the dock
Detaching the Surface Book from the dock results in an error (the most common being related to SearchUI)
Weird screen color temperature issue when scrolling web pages (see video below)
Random display driver errors displayed every 10 to 20 minutes
Random trackpad freezes

There are also shortcomings related to the hardware itself:

Problems physically connecting/disconnecting the dock, with some users ending up with the screen half-disconnected
A screen wobble due to a weight imbalance between the screen and keyboard
No ambient light sensor controlling the brightness of the backlit keys, something that most laptops - especially premium models - have these days
No quad-core CPU option for those wanting more power
Concerns about the strength of the hinge

Bugs are normal early on in a product's lifecycle, and I'm sure that many of these issues will be sorted out over the coming months. Remember also that the Surface Book is a new class of device, so you're also getting to experience all those first-gen bugs and issue.

However, for some of those who put down a few thousand dollars of their hard-earned cash to be one of the first to own a Surface Book, the experience has been far from smooth.

Several people have asked me whether I'm considering buying a Surface Book since I'm in the market for a mobile Windows-based system for a number of projects I have on the go. The answer is "no," and that's down to the fact that I try my best to avoid first-generation hardware if at all possible because, well, I find that I end up having to spend too much time nursing it as opposed to just using it.