Scali wrote:

upgrading Windows

There we go, problem detected 😜

Tetrium wrote:

It's very common knowledge that upgrading existing installs of Windows may cause all kinds of trouble.

You mean upgrades in general. Windows generally actually does a pretty decent job, as long as you don't have any strange hardware/drivers/applications that break things. Which I have 99% of the time. Which is why all my Windows 10 upgrades have been problem-free up to now (and I've upgraded my pool of machines from Windows 7 to Windows 10 when it first came out, and all Win10 upgrades up to now).

Tetrium wrote:

But I guess you just wanted to point the blamy finger at AMD again like you do every chance you get.

Sadly, the facts contradict you. Clearly I originally suspected F-Secure rather than AMD.
I only blamed AMD after I had solved the issue, and had thereby verified that AMD was the root cause. So it was an established fact at this point. It's not my fault that AMD is to blame for this issue. Don't shoot the messenger.
It's getting annoying that you have to go on your defamation rants everytime some less-than-favourable facts about AMD are posted.

Tetrium wrote:

Scali wrote:

upgrading Windows

There we go, problem detected 😜

And he thought a older driver would work on windows 10? No really if you upgrading remove everything you can from the system, then do the upgrade.

Infact I had a Dell M2800 at work I just installed windows 10 on about a week ago, I never had any problems. But I did a clean install.

Jade Falcon wrote:

And he thought a older driver would work on windows 10?

Firstly, no, it was the latest driver from AMD available. Since it's a FirePro, AMD offers drivers specifically for my laptop model.
Secondly, my Core2 Duo laptop from 2007 works fine with a driver from 2010. So older drivers can indeed work fine in Windows 10. The problem was some kind of bug in the driver, since it's a dual-GPU configuration. It didn't come out of sleep-state or whatever.

Jade Falcon wrote:

No really if you upgrading remove everything you can from the system, then do the upgrade.

Didn't have to do that on any of my other Windows 10 machines. Which obviously is the idea, since the Creators Update is just offered via Windows Update.

Jade Falcon wrote:

Infact I had a Dell M2800 at work I just installed windows 10 on about a week ago, I never had any problems. But I did a clean install.

Obviously my M2800 already ran Windows 10 (and handled the earlier updates properly, for some reason). It's just the update from Anniversary to Creators that was troublesome.

I did not have any problem with the Creators update on the system. I think your doing something wrong.

And wile sometimes drivers from older windows OS's will work on newer OS's, its not always the case.

Jade Falcon wrote:

I did not have any problem with the Creators update on the system. I think your doing something wrong.

I'm not doing anything wrong. As I said, once I removed the offending driver, the update went through just fine, like on all my other systems.
I could even re-install the AMD drivers afterwards, and it didn't crash.
But there is some glitch in these drivers that is triggered during the upgrade at exactly 32%. I've tried it at least 5 times, disabling various devices in the UEFI setup, making sure all drivers were up-to-date, removing possibly troublesome software such as F-Secure, doing a disk scan, making sure the Windows image is not corrupt with dism etc.
The only thing that eventually worked, was removing the (up-to-date) AMD driver.

Jade Falcon wrote:

And wile sometime drivers from older windows OS's will work on newer OS's, its not always the case.

Obviously, and I wouldn't complain if my Core2 Duo didn't work. Fact is however, it did work, while the AMD FirePro (yes, that's even the professional line, not the consumer line, this is not a budget laptop) did not.

I did not have to do anything with the FirePro drivers to install the creators update. it's obvious you did something wrong or something is wrong with the laptop if you had to remove it.

Jade Falcon wrote:

I did not have to do anything with the FirePro drivers to install the creators update. it's obvious you did something wrong or something is wrong with the laptop if you hade to remove it.

But you did a clean install, you just said. So you didn't have any FirePro drivers on your system until after the Creators Update was installed.

Scali wrote:

Jade Falcon wrote:

I did not have to do anything with the FirePro drivers to install the creators update. it's obvious you did something wrong or something is wrong with the laptop if you hade to remove it.

But you did a clean install, you just said. So you didn't have any FirePro drivers on your system until after the Creators Update was installed.

No I did a clean install of windows 10, after witch I installed the security software and drivers then the creators update.

Jade Falcon wrote:

No I did a clean install of windows 10, after witch I installed the security software and drivers then the creators update.

Then you may have just been lucky. I don't see what point you're trying to make.
Nothing you say or do will change the fact that my Creators Update froze my machine at 32% everytime, until I uninstalled the FirePro drivers and software. I only got that idea because I read the advice from other people to completely uninstall all video drivers, dealing with the same problem. So apparently I'm not alone in this.
Which doesn't mean it has to happen to everyone everytime, but I never claimed that anyway.

Scali wrote:

Then you may have just been lucky. I don't see what point you're trying to make. Nothing you say or do will change the fact that […]
Show full quote

Jade Falcon wrote:

No I did a clean install of windows 10, after witch I installed the security software and drivers then the creators update.

Then you may have just been lucky. I don't see what point you're trying to make.
Nothing you say or do will change the fact that my Creators Update froze my machine at 32% everytime, until I uninstalled the FirePro drivers and software. I only got that idea because I read the advice from other people to completely uninstall all video drivers, dealing with the same problem. So apparently I'm not alone in this.
Which doesn't mean it has to happen to everyone everytime, but I never claimed that anyway.

Funny thing is I have a few system with the same Firepros and not one had a problem with the creators update.
I still say something was wrong on your end. I mean I had 3 systems with a m4170 and not one had problems with the creators update.

Jade Falcon wrote:

I still say something was wrong on your end.

Something was obviously wrong.
It was solved by removing all FirePro drivers and software.

Scali wrote:

Jade Falcon wrote:

I still say something was wrong on your end.

Something was obviously wrong.
It was solved by removing all FirePro drivers and software.

But basted on my Dell M2800 you should not have had to remove the drivers. That's more the point I'm getting at more then anything. There must have been something deeper then just the derivers

Jade Falcon wrote:

But basted on my Dell M2800 you should not have had to remove the drivers. That's more the point I'm getting at more then anything. There must have been something deeper then just the derivers

I don't see why. You and I may not have used the exact same drivers, or we may not have used them in the exact same way (I have upgraded mine a few times, perhaps an earlier driver upgrade caused the problem... perhaps it's also one of the functions in the drivers I enabled or disabled, who knows).
So the fact that it works on your machine doesn't prove the drivers are bug-free.
That's a lesson that every programmer should learn early in life: working code is not bug-free code.