New
#120
Hello all here,
I am a new member and almost a senior citizen from down under..I have looked through this fantastic website whenever I had issues and most of the time I got the answer to my problems, so I thought I should JOIN rather than be a leach
In relation to my experience with Skippy 17661.1001 on everyone of my 6 PC's with W10 Pro 64, (Dell E5530, M17X, and Others) they ALL hung at 100% for hours and then the install was all over the place (% wise), so I got sick and tired of 'waiting' and decided to download the ISO, and manually install, way faster..
Now to the whinge, what the heck is wrong with MS, I know Skip users are the 'testers' but seriously this is just ridiculous, they can not see the 'install hanging' issues that almost all have posted, why release this build when there is an obvious issue with running it, WHY, some have taken over 4 hours and still show problems or failures.
it is just NOT GOOD ENOUGH....Period!
A member posted an issue with BT and Sound, every time I ' feature update' my MS build I have to uninstall my Intel BT Driver (in Device Manager) and then reboot, then driver is auto installed and all is fine.
Have reported this issue as I am sure many others have but it still persists and never see any reply or acknowledgement.
LOCATION
Another issue I have found on all of my PC's is when I check my device location it comes up somewhere in Portugal (Northern Hemisphere) when I am located in the South of Australia!.
Does not matter what I do, if I manually set 'time zone location' to off I can then set drop down to my real location, but usually when I set Time Zone to Auto ON, it will auto change to wrong country and location and time zone, when I do a my device search it will pinpoint to this wrong location, happened on previous builds and again something that MS can not rectify and they tend to blame the PC or operator when what I have read on MS own support pages and never appear to find any solution, like come on how can it show that my PC is 10,000 miles away!, if anyone else can assist I would be grateful.
Thank you :)
LOCATION
Another issue I have found on all of my PC's is when I check my device location it comes up somewhere in Portugal (Northern Hemisphere) when I am located in the South of Australia!.
Does not matter what I do, if I manually set 'time zone location' to off I can then set drop down to my real location, but usually when I set Time Zone to Auto ON, it will auto change to wrong country and location and time zone, when I do a my device search it will pinpoint to this wrong location, happened on previous builds and again something that MS can not rectify and they tend to blame the PC or operator when what I have read on MS own support pages and never appear to find any solution, like come on how can it show that my PC is 10,000 miles away!, if anyone else can assist I would be grateful.
Thank you :)
Went amazingly smoothly on the physical machine. Maybe 1 1/2 hrs at most to the restartt prompt. Making the ISO now. I'll be out of town over the weekend so this is a welcome development
Nah. The damn thing reboote when making the ISO was at 95%. Second try rebooted at 87%. All and all Skippy is far more unstable than Debian Experimental for pete's sake. Now the VMs are not even picking up the upgrade. And they asked me to verify my identity by entering my password.
I'm just going to pickup a warez copy of 17661.1001 - but if anybody has succeeded in making an ISO please PM me - TIA
Last edited by martyfelker; 04 May 2018 at 00:41.
I gave up after 4+ hours. I will let it try to update overnight and maybe it will be done by the time I wake up. :-|
Preparing to install 100%: Over an hour
Preparing to install 80%: Over an hour
Preparing to install 80% again: Over an hour
and this is on Microsoft hardware, Surface 4..... I'm done with this nonsense.
It took about 5 Hrs to complete and this is the longest ever install for me.
Didn't happen in 17655 but here it's again, a known problem with Ryzen platform, after reboot it always defaults to Balanced Power Plan. New chipset drivers didn't help. Speaking of drivers, it changed my GPU drivers to much older version, from 18.3.1 to 17.7 which is default MS (distributed and signed) driver from a year ago.