October 1809 Update for Windows 10

Interestingly the rest of that announcement also seems to point to the manual installation using Update Assistant being the problem, with Check for Updates not given the same emphasis.

Quote
<div class="ipsQuote_contents">
	<p>
		<span><span><span>If you have checked for updates and <strong>believe</strong> you have an issue, please contact </span></span></span><span><span>us<span> directly at .......</span></span></span>
	</p>
</div>
Quote
<div class="ipsQuote_contents">
	<p>
		<span><span><span>If you have <strong>manually downloaded</strong> the <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsoftware-download%2Fwindows10&amp;data=02%7C01%7CChristine.Ahonen%40microsoft.com%7C3f757180e5ee4f19319208d62b3f52fa%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636743948310218747&amp;sdata=wsczTYD5ttMDKHKwFu0duKTU17kqcJeQEeYa7eHtMWM%3D&amp;reserved=0" rel="external nofollow"><span><u>Windows 10 October 2018 Update installation media</u></span></a></span></span></span><span><span>, please <strong>don’t install it</strong> and wait until new media is available.</span></span>
	</p>
</div>

Of course if people made backups of their files then it would not be a problem.

(I saw one guy shouting that he had lost 23 years worth of work files - Really? Never backed up your work files in 23 years?)

done 7 PC's now, no issues. doing them all from a USB stick with the ISO from the Media Creation Tool.

only one very minor thing, on 3 of the PC's it made the desktop background the solid black colour whereas I always set mine to the solid blue.

so all-in-all, a painless experience so far.

just have 2 laptops to go... :)

It does seem to be a problem with using Update Assistant before the upgrade is fully compatible with certain machines.

If you try to 'force' the update yourself before MS says it's ready for your machine then you may have problems.

From what I've seen online if it isn't showing up in 'Updates & Security > Windows Update' it should be left alone.

The person that lost 23 years of work, that was supposedly 220 GB worth, couldn't imagine even trying to backup all that 23 years ago -- but nowadays it wouldn't even make a dent on a high capacity HDD that costs a mere $40 USD, hell it would even fit comfortable on a 256 GB flash drive.

Well it won't show now in 'Check for Updates' because it's been pulled altogether.

The problem does seem confined to those who downloaded to media and installed it themselves, - and they probably did that because it wasn't being offered to them by 'Check for Updates'.

Which of course suggests that it was not compatible with their particular setup yet, or they would have been offered it.

It's also possible that it may have been a problem with the 'Install from media' rather than with Windows10 1809 itself?

Anyone who has done this to update an existing Windows installation will know there are options to 'Keep personal files and apps', 'Keep personal files only', or 'Keep Nothing'.


Maybe that choice was not being respected and it just wiped the files? (Or maybe the affected users simply made the wrong choice?).

As reported above Recuva is usually able to get the deleted files back.

I think the real problem was they knew months ago that it was deleting files, but somehow never fixed that and released it anyways. Can't think of a better mishap for them to tarnish Windows beyond what it already is and cause some people migrate over to Linux or MAC.

I can just imagine a MAC TV commercial with the slogan: Your files are safe!

Quote
<div class="ipsQuote_contents">
	<p>
		cause some people migrate over to Linux or MAC
	</p>
</div>

Have you seen what's going on with Linux recently?

BTW. Win10 1809 installed normally on my laptop (through Check for Updates) and is working fine in everyday use.

"It appears the bug that caused file deletion was related to Windows 10 users who had enabled Known Folder Redirection to redirect folders like desktop, documents, pictures, and screenshots from the default location."

The Verge: Microsoft begins re-releasing Windows 10 October update after fixing file deletion bug.

https://www.theverge.com/2018/10/9/17957506/microsoft-windows-10-october-2018-update-data-deletion-fix

For some reason the Verge site doesn't like me :(

In case anyone else has issues with that site here is another site with the info above Nergal mentions

https://blogs.windows.com/windowsexperience/2018/10/09/updated-version-of-windows-10-october-2018-update-released-to-windows-insiders/

8 hours ago, hazelnut said:
<div class="ipsQuote_contents">
	<p>
		For some reason the Verge site doesn't like me <img alt=":(" data-emoticon="" height="20" src="<fileStore.core_Emoticons>/emoticons/default_sad.png" srcset="<fileStore.core_Emoticons>/emoticons/sad@2x.png 2x" title=":(" width="20"></p>
</div>

Look at other YouTuber's reaction to The Verge's YouTube video on how to build a $2000 PC, and be glad that site doesn't load for you.;)

The woes continue

https://www.zdnet.com/article/more-windows-10-october-update-woes-hp-users-report-bsod-after-tuesday-patch/

Maybe they should've waited at least 30 days after that first incident, and scoured through it looking for more bugs before making it available again. If it's offered on my system I'm going to wait a good while before allowing it to install.

Remember that 1809 was not pushed out to users 'Automatically', - you had to go and get it either by manually 'Checking for Updates', using the Apdate Assistant, or downloading media and installing yourself.

It was pulled before it was sent to users automatically, and is still on hold - the 'new' version is only available to Windows Insiders.

TBH the missing files problems only affected those who had set Known Folder Redirects.

Not something the average home user would even know how to do, and of course the average home user would have waited for the Automatic Update rather than doing it manually as an early adopter.

I'm not sure about the HP problem, but again anyone seeing this must be an early adopter who downloaded/installed 1809 manually.

Being an early adopter of anything always comes with the risk of possible problems.

The 1809 update was and still is on the Microsoft website.

All anyone needed to do was to download Media Creator 1809.

Upon execution you could :

1 - UPDATE THIS PC

2 - CREATE MEDIA TO UPDATE ANY WINDOWS 10 COMPUTER EITHER ON DVD OR USB

3 - CREATE ISO FOR LATER USE

I chose #3, saving the ISO on my D: drive. Copied the ISO to a USB drive. Performed my own backup and SYSTEM RESTORE POINT. Mounted the ISO and ran the update.

My computer updated without any problems, what so ever, which is a FIRST for WINDOWS 10 PRO X64 !!!

It only took me 1 hour to update which I feel was a little long in the tooth....

Pete...

11 hours ago, MENINBLK said:
<div class="ipsQuote_contents">
	<p>
		The 1809 update was and still is on the Microsoft website.
	</p>
</div>

Not on the standard user website it isn't.

v1809 was there for a few days but it was pulled and it is v1803, the April 2018 Update, that is currently available on the Update Assistant/Media Creation page.

https://www.microsoft.com/en-gb/software-download/windows10

There is a 'new' version of 1809 available to Windows Insiders only, but that's not yet on general release.

https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced

Even more woes (and three terrible ideas for a fix)

https://www.windowscentral.com/how-restore-internet-access-apps-after-windows-10-october-2018-update

I wonder just how many users (not insiders) actually have 1809 Release to Market version?

I do and haven't had any problems with it. (Currently build 17763.55)

I can't find any statistics for the number of 1809 RTM updates/downloads that were made.

Remember 1809 RTM was only available if you manually used 'Check for Updates', used Update Assistant, or downloaded media - (ie. it wasn't released as an Automatic Update).

And it was only available for 3 days.

I've so far installed it on 9 desktops and 5 laptops, over half of those had SSDs so they had default folder redirection in use and I've had no issues with the process.

have also done two domain connected PC's and all went smoothly.

13 hours ago, nukecad said:
<div class="ipsQuote_contents">
	<p>
		Remember 1809 RTM was only available if you manually used 'Check for Updates', used Update Assistant, or downloaded media - (ie. it wasn't released as an Automatic Update).
	</p>
</div>

If someone manually uses Check for updates in Updates & Security it really makes no sense to offer it in my opinion, and why isn't it just fetching normal Automatic Updates like security patches, Windows Defender updates, etc., that a user can manually invoke at a given time because they have the time.

I don't really understand why it isn't one of those things where it will only get offered via an Automatic Update regardless if something manually clicks Check for updates. Maybe they should seriously re-think how Check for updates works!

21 hours ago, nukecad said:
<div class="ipsQuote_contents">
	<p>
		I wonder just how many users (not insiders) actually have 1809 Release to Market version?


		I do and haven't had any problems with it. (Currently build 17763.55)
	</p>

	<p>
		I can't find any statistics for the number of 1809 RTM updates/downloads that were made.
	</p>

	<p>
		Remember 1809 RTM was only available if you manually used 'Check for Updates', used Update Assistant, or downloaded media - (ie. it wasn't released as an Automatic Update).


		And it was only available for 3 days.
	</p>

	<p>
		 
	</p>
</div>

I'm on the same build you are and have not had any issues. The only glitches -- the timestamp for Windows Defender definitions is off by several hours on the user interface (but not on Windows Update) and CCleaner's inability to clean everything that's checked (stems from 1809 and I reported that in the 'bug' section. Piriform is working on a fix).