|
|
Post by MartinT on Jul 10, 2020 7:17:03 GMT
|
|
|
|
Post by Tim on Jul 10, 2020 7:59:25 GMT
The BIOS has a signature which I believe they use, too. I know Martin, but it wasn't the same BIOS. The board that died was a Gigabyte and I replaced it with an ASRock, so two different BIOS versions, from different years and manufacturers'. That was always my original belief, if you changed the motherboard, you needed to enter a valid licence key again to activate.
On further thought though, there is one more factor, which Slinger was suggesting. It isn't the same 'actual' installation media, but it was the same version of Windows. The install from March 2016 was an ISO download direct from Microsoft, as I upgraded all my hardware to Windows 10 before putting it in storage. The installation the other day was again version 1511, but the ISO image came from Rufus.ie via their program where you can download older copies of Win 10 and 8.1. So Slinger is right in a way, it wasn't the same ISO or the same USB stick from 2016, but it was the same version of Win10, if that makes sense?
Haha, I've got faaaaaar too much time on my hands if I'm trying to work this out  and to be honest ... |
|
|
|
Post by MartinT on Jul 10, 2020 8:41:27 GMT
Ah, ok. Do you use a Microsoft account? That tends to keep things joined up. Otherwise, your downloaded W10 may be pre-activated.
I must admit I've been blase about activation as I always have access to W10 and activation codes at work, so I've never worried about it.
|
|
|
|
Post by Tim on Jul 10, 2020 8:57:49 GMT
Ah, ok. Do you use a Microsoft account? That tends to keep things joined up. Absolutely not Martin, good grief!
When I install a fresh copy I don't have a connection to the internet, don't enter a key, say no to absolutely everything and after first boot I strip out all the crap. My user name is User too.
I like to keep it simple  |
|
|
|
Post by MartinT on Jul 10, 2020 9:14:41 GMT
Standard paranoid mode!
|
|
|
|
Post by Tim on Jul 10, 2020 9:36:31 GMT
Haha, well after 36 years in a working life where I've been more accountable than most, I prefer to keep my footprint as small as possible now. Working in computer forensics didn't help either! I think the biggest thing is I don't like having anything assumed or done for me, without my permission - I think it's polite to ask first.
Google knows everything about me anyway, so Microsoft can know a little less So I'll drink to standard paranoia. |
|
|
|
Post by Slinger on Jul 15, 2020 15:36:00 GMT
I thought I'd give manually requesting the update another go. After much huffing and puffing, and many messages telling me that it was getting on with the job, culminating in downloading (it said) any updates required, it spat this out. So it seems that what needs my attention is actually nothing, despite their use of very large characters which are the same colour as their links, but aren't a link, because my PC setup is just too advanced for their silly little operating system.  |
|
|
|
Post by Tim on Jul 15, 2020 17:08:36 GMT
What version are you on Slinger?
|
|
|
|
Post by Slinger on Jul 15, 2020 17:24:09 GMT
1909, Tim.
|
|
|
|
Post by MartinT on Jul 15, 2020 18:23:41 GMT
But, in all fairness, you knew that already Paul. We're all waiting and the issues are caused by drivers, which need updating by the vendors.
|
|
|
|
Post by speedysteve on Jul 15, 2020 18:53:44 GMT
I use a program called Hornresp 😀
It's for modelling horns (the acoustic kind).
It's very good. You input the driver T&S params, tell it what sort of horn shape / profile you'd like, the cutoff frequency and it will calculate the shape, throat and mouth areas, show you the acoustical power (dB Vs Freq), max driver excursion, distortion, phase etc.
It will even output a crude cutting list!
Once built, the horn will measure very close to the simulation. It's that good!
Anyway, it's been going for years.
After my forced conversion from HDD to SSD (thank you MS, for so much landfill across the world), I needed to download and install it again.
Download no problem. As soon as I went to install it Defender took exception and said it was malware, and even deleted the application from my pc!
No matter what I tried no dice.
I know the developer and a very nice chap he is too!
Mailed him, he's still on W7!
I tried downloading via other browsers, installing as sys admin etc..
I either downloaded via Edge instead of Chrome, or was it Opera and finally by magic it installed. No idea why!
It works just fine of course.
David mused some more, and it a might be the query that checks if it's the latest version Vs the one of the web, and MS might see that as malware.
He's pondering what to do.
I read on the Diyaudio thread, one other guy has had the same problem!
|
|
|
|
Post by Slinger on Jul 15, 2020 18:58:34 GMT
But, in all fairness, you knew that already Paul. We're all waiting and the issues are caused by drivers, which need updating by the vendors. In all fairness, Martin, no I didn't. You might have access to that sort of information but as a lone end user I'm completely in the dark about Microsoft's whims and fancies. I'm not a part of the "We all," that counts. |
|
|
|
Post by MartinT on Jul 15, 2020 19:00:38 GMT
I'm still waiting for it on my Surface, if that makes you feel any better. It's going to depend on the vendors reworking their drivers. It does. Thank you. Not only did I tell you, but you responded |
|
|
|
Post by Slinger on Jul 15, 2020 19:14:32 GMT
Yup, several weeks ago. I had no way of knowing if the situation had changed, which is why I gave it another go. By posting about it I hoped to make sure other people didn't bother yet.
|
|
|
|
Post by MartinT on Jul 15, 2020 19:20:50 GMT
By posting about it I hoped to make sure other people didn't bother yet. We won't! But seriously, the warning about your machine 'not being quite ready' for the 2004 update will go away once the particular driver that is a problem in the machine has been updated. |
|
|
|
Post by Slinger on Jul 15, 2020 19:25:26 GMT
I'll just have to wait for them to catch up with me I suppose, and then hope that they tell me they've done so. |
|
|
|
Post by MartinT on Jul 15, 2020 20:22:31 GMT
There is that, but my Surface Pro 7 stubbornly refuses to update so I'll be patient and wait for them.
|
|
|
|
Post by pre65 on Jul 16, 2020 7:46:51 GMT
There is that, but my Surface Pro 7 stubbornly refuses to update so I'll be patient and wait for them.
So, after it was finished I tried to manually update to 2004. Initially it said the machine was suitable, but after a while I got a message to say the update was halted, because the machine was not ready yet.
So, guess it will wait till "whatever" is updated.
Is there no way to find out what is causing the delay ? |
|
|
|
Post by MartinT on Jul 16, 2020 7:59:47 GMT
|
|
|
|
Post by Tim on Jul 16, 2020 8:33:57 GMT
I'll just have to wait for them to catch up with me I suppose, and then hope that they tell me they've done so. Personally Paul, I wouldn't be in any sort of a rush to install a new version of Windows until I can Google it and not get pages and pages of current reported issues. You don't need 'to be in the know' to use Google old chap If you have a spare HDD lying around (always a good idea to have a test drive), pop that in in place of your current boot drive and install Version 2004. You can get it here - www.microsoft.com/en-gb/software-download/windows10 That is version 2004 too, as I checked and installed it on a Asus laptop, it did work OK, but it's only 18 months old, so driver issues were unlikely especially with an Asus machine. Bung it on a USB stick, boot up and thoroughly test everything first without any risk . . . you know it makes sense |
|
and to be honest ...
