The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Given that the new operating system from Microsoft seems to be quite a popular topic at the moment, it's probably worth sharing any knowledge we have as we all install and "road test".
So, tell us if you've been successful, what you think of it, or alternatively if you've encountered problems both installing and following the install.
If you have come across any fixes or workarounds, tell us about those too.
So, tell us if you've been successful, what you think of it, or alternatively if you've encountered problems both installing and following the install.
If you have come across any fixes or workarounds, tell us about those too.
Page:
So sorry to read of your problems Hmmm ... we've 4 pc's/laptops and 2 tablets here and no problems at all with any 'upgrades'! Not even seen any 'major upgrades' mentioned in W10 upgrade list.
Nice to see that your dad is still active ... mine died a year ago ... 90 and a half :¬(
Nice to see that your dad is still active ... mine died a year ago ... 90 and a half :¬(
Messing about with my daughter's laptop at the moment - updating it to Windows 10 'version 1511 November Update'.
It's not a quick job - looking at the logs I can see the update has failed "Error"! a few times. After poking things about, crashing a 'starting loop' like lots of others I seem to be winning!
NB. This is a 3+GB download - for me as big as the update from W7 > W10. If Microsoft do this for each Service Pack (I mean big monthly update) it will be a bit of a pain.
Updating pic!
Can't help wondering if Microsoft have got this 'no more versions numbers' thing right! In the old days this would have been known as 'SP1'.
When trying to troubleshoot problems I can see this getting confusing. In the end the people fixing things will no doubt still need to know which version/update the PC is on they'll just have to look a little bit harder to see it!
Tip cmd window and type: ver is probably the quickest way.
Edit: perhaps not so good. This gives the build number but I had to use Settings About option to see the 1511 version.
I'm posting this from my old faithful XP SP3 machine that's running just fine after turning off Windows Updates 18 months ago just before MS withdrew support. At the same time I'm backing it up using SyncBack (see my Freeola SyncBack post) to a trusty not-quite-so-old Vista PC!
21st Century
This week I'm installing a nice touch screen i7 jobbie for my 90 year old dad :¬)
Edit:
All finished but it wasn't painless!
Perhaps I was unlucky but after allowing Windows to update I was left with an unresponsive Desktop and after being very patient had to crash/power off the PC. I was left with a partial Desktop (Taskbar only) and had to crash it again. It will now Shutdown/Restart normally... But not a great experience.
It's not a quick job - looking at the logs I can see the update has failed "Error"! a few times. After poking things about, crashing a 'starting loop' like lots of others I seem to be winning!
NB. This is a 3+GB download - for me as big as the update from W7 > W10. If Microsoft do this for each Service Pack (I mean big monthly update) it will be a bit of a pain.
Updating pic!
Can't help wondering if Microsoft have got this 'no more versions numbers' thing right! In the old days this would have been known as 'SP1'.
When trying to troubleshoot problems I can see this getting confusing. In the end the people fixing things will no doubt still need to know which version/update the PC is on they'll just have to look a little bit harder to see it!
Tip cmd window and type: ver is probably the quickest way.
Edit: perhaps not so good. This gives the build number but I had to use Settings About option to see the 1511 version.
I'm posting this from my old faithful XP SP3 machine that's running just fine after turning off Windows Updates 18 months ago just before MS withdrew support. At the same time I'm backing it up using SyncBack (see my Freeola SyncBack post) to a trusty not-quite-so-old Vista PC!
21st Century
This week I'm installing a nice touch screen i7 jobbie for my 90 year old dad :¬)
[s]Hmmm...[/s]Edit:
All finished but it wasn't painless!
Perhaps I was unlucky but after allowing Windows to update I was left with an unresponsive Desktop and after being very patient had to crash/power off the PC. I was left with a partial Desktop (Taskbar only) and had to crash it again. It will now Shutdown/Restart normally... But not a great experience.
Now is that Shadow Warrior or Shadow Warrior (Classic)? :)
Shadow Warrior on Insane setting Edgy ... that's what you said would be next up on your 'Quest' ;¬)
Just playing it now on Insane and it's awesome :¬)
Just playing it now on Insane and it's awesome :¬)
That's in my Steam Library - will be giving it a go :)
I'm currently attempting Age of Empires 3 (which, apart from a few moments of slowdown, seems to work fine) but I may put Shadow Warrior as my next one (as alphabetical order will suck)
I'm currently attempting Age of Empires 3 (which, apart from a few moments of slowdown, seems to work fine) but I may put Shadow Warrior as my next one (as alphabetical order will suck)
Shadow Warrior ... a dream :¬)
I attempted it but it still wouldn't work without me reverting to the compatibility mode. The good thing is, it didn't require doing anything fiddly - it worked with standard Windows 8 compatibility mode so I'm happy.
Edgy wrote:
First compatibility issue I have encountered:
Ace Combat: Assault Horizon Enhances Edition - I had to run in Windows 8 compatibility mode. The problem was some sort of graphics issue making my screen turn very white, occasionally blurring in the actual game graphics. This didn't happen in the menus however.
If it's a Steam game, try verifying the local files. Works a treat for a number of Steam game problems after the W10 upgrade.
First compatibility issue I have encountered:
Ace Combat: Assault Horizon Enhances Edition - I had to run in Windows 8 compatibility mode. The problem was some sort of graphics issue making my screen turn very white, occasionally blurring in the actual game graphics. This didn't happen in the menus however.
If it's a Steam game, try verifying the local files. Works a treat for a number of Steam game problems after the W10 upgrade.
First compatibility issue I have encountered:
Ace Combat: Assault Horizon Enhances Edition - I had to run in Windows 8 compatibility mode. The problem was some sort of graphics issue making my screen turn very white, occasionally blurring in the actual game graphics. This didn't happen in the menus however.
Ace Combat: Assault Horizon Enhances Edition - I had to run in Windows 8 compatibility mode. The problem was some sort of graphics issue making my screen turn very white, occasionally blurring in the actual game graphics. This didn't happen in the menus however.
Re. Cortana
It will probably never be used in anger - but if it's part of W10 it seemed worth getting it to work.
It will probably never be used in anger - but if it's part of W10 it seemed worth getting it to work.
[s]Hmmm...[/s] Page: