If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#31
|
|||
|
|||
Windows 10 1809
On 10/24/2018 11:01 AM, Weatherman wrote:
Dick wrote: On 10/24/2018 5:49 AM, Neil wrote: On 10/24/2018 2:46 AM, Big Bad Bob wrote: On 10/15/18 12:24, Neil wrote: On 10/15/2018 12:22 PM, Bill Bradshaw wrote: With all the reported problems has Microsoft stopped pushing out the 1809 update?Â* None of the computers have been updated from 1803 to 1809. It was never pushed, AFAIK. no, just shoved up everyones ASS, as usual [without lubrication]. Forced updates *SUCK*.Â* WORST! IDEA! EVAR! [2nd worst was putting ADVERTISEMENT and SLURP into the OS, 3rd worst was 2D FLATSO FLUGLY, ...] AFAIK, it STILL hasn't been pushed. All of my Win10 machines are still on 1803. I suspect that those running 1809 are either voluntarily or unwittingly involved in the insider program. Hey guys, I received the 1809 thru normal Windows updates on Oct 3rd. Actually, I was surprised when both my main workstation and my laptop came up with a "Want to schedule a restart today?".Â* I looked around and sure enough it had installed on both machines (unknown to me). So I did a restart on each and everything came up just fine. A couple of days later, I heard all the bru-ha about it being pulled. So far I have seen no problems and my Android Studio workbench seems to be speedier during compiles.Â* So far, I'm pleased. Dick The problem occurred for those who moved their default Downloads, Documents, Videos, etc. folders to another drive or partition. 1809 deleted everything in those folders. You obviously didn't do that. Weatherman, You are correct. My user profiles are all plan vanilla. dick |
Ads |
#32
|
|||
|
|||
Windows 10 1809
Big Bad Bob wrote:
On 10/15/18 09:22, Bill Bradshaw wrote: With all the reported problems has Microsoft stopped pushing out the 1809 update? None of the computers have been updated from 1803 to 1809. https://www.theregister.co.uk/2018/1...ows_10_crisis/ that kinda says it all But that article is just "piling on for $1 a word". Peter Bright wrote a piece for Ars that kicked this off, and it's likely a better article to be reading. Traditional "test" and "testers" will not fix the current problems. Testers have limited purview. They are not allowed to argue with architecture-class employees, neither are they allowed to second-guess management decisions. Their job is simple. Compare "expected results" to "actual results", and report any differences. Human testers are used, when it's not possible or practical to automate testing. At least some of what is happening, is when "dumb ideas" get approval. It's like there is a missing layer of intelligence (middle managers) to stop certain things from happening. Deleting the targets of some disconnected Junction Points, without checking what is inside them, is an example in point. And I don't think test works the way we think it does at Microsoft. The Insiders are not a significant factor as far as testing goes. The RTM/Release that ships, is not the same thing that a similarly stamped item on the Insider ring shows. Insiders have been used a few times for A/B testing, but other than that, I'm not sure they have a really solidly defined position in the picture. They're a parallel structure of some sort. Since the Insider population will not remain constant over time, you have to allocate resources you can rely upon to be there when you need them. And an Insider is not that person. They could be using "designer test and dogfooding" for all I know. We used dogfooding at work for the stuff we used to spin in the computer domain. There's a certain sense of dread, when a new release comes out. "Will it spoil my day?" "Will this cost me time from my schedule?" Well, stay tuned. Your dogfood is on its way. You couldn't say no, to freshly served dog food. Paul |
#33
|
|||
|
|||
Windows 10 1809
Weatherman wrote:
Dick wrote: On 10/24/2018 5:49 AM, Neil wrote: On 10/24/2018 2:46 AM, Big Bad Bob wrote: On 10/15/18 12:24, Neil wrote: On 10/15/2018 12:22 PM, Bill Bradshaw wrote: With all the reported problems has Microsoft stopped pushing out the 1809 update? None of the computers have been updated from 1803 to 1809. It was never pushed, AFAIK. no, just shoved up everyones ASS, as usual [without lubrication]. Forced updates *SUCK*. WORST! IDEA! EVAR! [2nd worst was putting ADVERTISEMENT and SLURP into the OS, 3rd worst was 2D FLATSO FLUGLY, ...] AFAIK, it STILL hasn't been pushed. All of my Win10 machines are still on 1803. I suspect that those running 1809 are either voluntarily or unwittingly involved in the insider program. Hey guys, I received the 1809 thru normal Windows updates on Oct 3rd. Actually, I was surprised when both my main workstation and my laptop came up with a "Want to schedule a restart today?". I looked around and sure enough it had installed on both machines (unknown to me). So I did a restart on each and everything came up just fine. A couple of days later, I heard all the bru-ha about it being pulled. So far I have seen no problems and my Android Studio workbench seems to be speedier during compiles. So far, I'm pleased. Dick The problem occurred for those who moved their default Downloads, Documents, Videos, etc. folders to another drive or partition. 1809 deleted everything in those folders. You obviously didn't do that. It would the the orphan from the Junction Point which gets deleted. It doesn't delete the Downloads, Documents, Videos. It deletes the *former* Downloads, Documents, Videos, before you moved the Junction Point. At least a few people, carrying out such an operation manually, would ask themselves "should I move those files to the new storage location?". And of course the answer was yes, because they were on a mission to save space. Anyone with the skills to move a Junction Point, would realize the significance of the "previous value" in the interface. The people who actually got caught, were the cases where the OneDrive program moves the Junction Point as part of OneDrive setup (user does not know this is happening). What's in the Orphan directory in that case ? Who knows. You'd have to ask Microsoft that, as it would be up to the OneDrive code to exhibit proper hygiene and transfer the orphan directory contents to the new storage location, before pulling the Junction Point switch. You would need to find a couple actual examples of data loss, by people with a clue, to understand just what kind of content is getting lost. I believe people, that they're losing stuff. It would help though, if we had confirmation it was mostly OneDrive users getting clobbered. Then we'd have to ask what the hell the OneDrive code was doing, before the Junction Point switcheroo. The Sysinternals.com "Junction" program can display your Junction values, if you want to observe them. Paul |
#34
|
|||
|
|||
Windows 10 1809
On 10/24/2018 6:42 PM, Paul wrote:
Weatherman wrote: Dick wrote: On 10/24/2018 5:49 AM, Neil wrote: On 10/24/2018 2:46 AM, Big Bad Bob wrote: On 10/15/18 12:24, Neil wrote: On 10/15/2018 12:22 PM, Bill Bradshaw wrote: With all the reported problems has Microsoft stopped pushing out the 1809 update?Â* None of the computers have been updated from 1803 to 1809. It was never pushed, AFAIK. no, just shoved up everyones ASS, as usual [without lubrication]. Forced updates *SUCK*.Â* WORST! IDEA! EVAR! [2nd worst was putting ADVERTISEMENT and SLURP into the OS, 3rd worst was 2D FLATSO FLUGLY, ...] AFAIK, it STILL hasn't been pushed. All of my Win10 machines are still on 1803. I suspect that those running 1809 are either voluntarily or unwittingly involved in the insider program. Hey guys, I received the 1809 thru normal Windows updates on Oct 3rd. Actually, I was surprised when both my main workstation and my laptop came up with a "Want to schedule a restart today?".Â* I looked around and sure enough it had installed on both machines (unknown to me). So I did a restart on each and everything came up just fine. A couple of days later, I heard all the bru-ha about it being pulled. So far I have seen no problems and my Android Studio workbench seems to be speedier during compiles.Â* So far, I'm pleased. Dick The problem occurred for those who moved their default Downloads, Documents, Videos, etc. folders to another drive or partition. 1809 deleted everything in those folders. You obviously didn't do that. It would the the orphan from the Junction Point which gets deleted. It doesn't delete the Downloads, Documents, Videos. It deletes the *former* Downloads, Documents, Videos, before you moved the Junction Point. At least a few people, carrying out such an operation manually, would ask themselves "should I move those files to the new storage location?". And of course the answer was yes, because they were on a mission to save space. Anyone with the skills to move a Junction Point, would realize the significance of the "previous value" in the interface. The people who actually got caught, were the cases where the OneDrive program moves the Junction Point as part of OneDrive setup (user does not know this is happening). What's in the Orphan directory in that case ? Who knows. You'd have to ask Microsoft that, as it would be up to the OneDrive code to exhibit proper hygiene and transfer the orphan directory contents to the new storage location, before pulling the Junction Point switch. You would need to find a couple actual examples of data loss, by people with a clue, to understand just what kind of content is getting lost. I believe people, that they're losing stuff. It would help though, if we had confirmation it was mostly OneDrive users getting clobbered. Then we'd have to ask what the hell the OneDrive code was doing, before the Junction Point switcheroo. The Sysinternals.com "Junction" program can display your Junction values, if you want to observe them. Â*Â* Paul All well and good, but I still find it curious that none of those having these problems have verified that they aren't in the IDK bunch (the closest was one who thought he may not be, but the "normal update process" would be expected for those that are. Meanwhile those of us (that I know of) that are *not* involved with the IDK have the message that our systems are "up to date" on 1803 (or older) and are not experiencing these problems. -- best regards, Neil |
Thread Tools | |
Display Modes | Rate This Thread |
|
|