Jump to content

Search the Community

Showing results for tags '1809'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 14 results

  1. The company largely stopped distributing the October 2018 Update in March, apparently deciding to simply skip one feature upgrade to solve the problem of two on a collision course. Microsoft / Valery Brozhinsky / Fermate / Getty Images Microsoft has given up on Windows 10 1809, the troubled feature upgrade of last year that was delayed by months, data from an analytics vendor showed. The Redmond, Wash. developer largely abandoned efforts to distribute the October 2018 Update, aka 1809 in its four-digit yymm format, last month, apparently deciding that it would, like many of its corporate customers, simply skip one feature upgrade to solve the problem of two on a collision course. According to AdDuplex, a Lithuanian company whose metrics technology is embedded in thousands of Windows Store apps, Windows 10 1809 powered just 26% of surveyed Windows 10 systems as of March 26. The gain from February to March, only 5 percentage points, was about half the increase from January to February, illustrating the slowing of 1809's adoption. "It looks more and more likely that Microsoft seems to be giving up on [1809] in favor of upgrading users straight to the next version," AdDuplex noted in a post its website. Because Microsoft decides how quickly an upgrade is adopted by controlling when consumers' PCs automatically download and install each refresh, it was clearly responsible for the slow uptake. (Microsoft did not give 1809 the "business ready" green light until after AdDuplex's data collection, ensuring that those who had installed it were largely consumers and very small businesses running Windows 10 Home or Windows 10 Pro. Microsoft controls the timing of upgrades on unmanaged PCs powered by those versions.) The dramatic slowing of 1809 adoption - when it should instead be accelerating - answered a question Computerworld posed last month: How would Microsoft address the problem of two upgrades released in close proximity? Upgrades collide The problem stemmed from the fiasco plaguing the October 2018 Update rollout. Although 1809 was initially released on Oct. 2, within days Microsoft purged it from the distribution pipeline because of upgrade-caused data loss. The company quickly returned 1809 to beta testing, and automatic dissemination didn't resume until Jan. 16, or about three months later than by a standard schedule. Because Microsoft forced Windows 10 Home users to accept feature upgrades when they were offered, the regimen was on an every-six-month cadence. But with 1809's automated distribution backed up by three months, the arrival of 1903 this spring was going to be hard on its heels. The company had to do something. Computerworld assumed two likely responses: Either Microsoft would require users to run 1809, no matter how briefly, before upgrading again to 1903, or Microsoft would skip 1809. AdDuplex's analytics indicated that Microsoft picked Option No. 2 no later than early March, when it must have begun slowing auto-delivery of 1809. Microsoft now plans to push out 1903 in late May. How Microsoft dealt with 1809 Microsoft made more than one move to quash Windows 10 October 2018 Update. First, it began to shut off the 1809 distribution spigot, slowing its adoption by unmanaged PCs running Home or Pro. That left the bulk of Windows 10 PCs powered by 1803, last year's spring upgrade. (AdDuplex's March tally said that 66% of all Windows 10 systems ran 1803.) It could have stopped there, enforcing the "no-1809" rule simply by refusing to release it to eligible PCs. (Managed machines running Windows 10 Enterprise, Education or Pro were, as usual, in the hands of organization IT administrators, who could be expected to skip the late-coming and problem-plagued 1809.) But Microsoft also announced that it would upend the update rules by giving owners of previously-unmanaged PCs - Windows 10 Home and Pro - the ability to manually manage feature upgrades. That pronouncement, made last week, spelled out a new update option, "Download and install now," for users of Windows 10 Home and Pro who rely on Windows Update. The option will let users decide when to download and install a feature upgrade; Microsoft will only intervene and initiate an auto-install when the version on the machine "is nearing end of support." "Download and install now" will be included with Windows 10 1903, but will also, Microsoft said, be added to 1803 and 1809 "by late May." In other words, users can themselves determine what version of Windows 10 they're running - within limits of support - rather than bending to Microsoft's will. Someone still running Windows 10 1803 in, say July, will be able to skip 1809 entirely by calling up "Download and install," which will then deploy the latest version, Windows 10 1903. As Figure 1 illustrates below, those running Windows 10 1803 will have several months - June through mid-November, when 1803 exits support - to leapfrog 1809 and install 1903. IDG/Gregg Keizer Figure 1: Users of Windows 10 1803 should have five months to make the move to 1903. Source: Microsoft throws in the towel on Windows 10 1809 (Computerworld - Gregg Keizer)
  2. With Windows 10 version 1903 just a month or so away, it is quite puzzling that a large number of devices have not yet received the update to Windows 10 version 1809. Microsoft began the rollout phase of Windows 10 version 1809 on January 16, 2019 but restricted automatic updates via Windows Updates. Only devices that the company believed to have the "best update experience" would receive the update back then. Administrators could run a manual check for updates and would receive the feature update then if no upgrade block was in place and if the device passed compatibility tests. Microsoft lists one upgrade block currently on the official update history page of Windows 10 version 1809. Devices who run "certain new Intel display drivers" are blocked from receiving the update via Windows Update. The solution right now is to update Intel display drivers so that they are newer than 24.20.100.6345. Microsoft updated the "Get the Windows 10 October 2018 Update" support page yesterday to indicate that the rollout of the new feature update for Windows has finally started. Windows 10 devices will receive the feature update automatically now provided that they are compatible with the new version and don't meet any upgrade block that may still be in place; this is true for devices with Windows Updates set to download and install updates automatically. Microsoft suggests that administrators run manual check for updates if the update is not offered automatically at this point. This is done by going to Settings > Update & Security > Windows Update, and activating the "check for updates" option on the page. It is still possible that the feature update is not returned when administrators run manual check for updates. Administrators may then download the Update Assistant from this Microsoft page to use it to update (or receive information on why an update is not possible). Closing words One has to wonder if it would not be better to sit this one out and wait for the release of the upcoming feature update. While it is certainly an option to upgrade to Windows 10 version 1809 and then a month or so later to Windows 10 version 1903, it is probably less time consuming to skip 1809 and wait for 1903 instead. Windows 10 version 1809 launched with major bugs and Microsoft had to pause the update for about six weeks. It is probably not a good idea to jump on the Windows 10 version 1903 bandwagon right after official release; far better to monitor the update for a month or two before making any upgrade decisions. (via Born) Source: Windows 10 1809: full rollout begins (gHacks - Martin Brinkmann)
  3. Microsoft announced today that they are now designating Windows 10 October 2018 Update Build 1809 to be ready for broad deployment, rather than targeted deployment. What a rough and unpleasant road the Windows 10 October 2018 Update has been down since it has been released with the numerous bugs, stops and starts in deployment, and an overall troublesome release. It looks like the journey is finally over and Microsoft has determined that Build 1809 is ready for broad deployment to all Windows 10 devices. "Based on the data and the feedback we’ve received from consumers, OEMs, ISVs, partners, and commercial customers, Windows 10, version 1809 has transitioned to broad deployment," stated Microsoft's Windows as a Service evangelist John Wilcox in an announcement. "With this, the Windows 10 release information page will now reflect Semi-Annual Channel (SAC) for version 1809. We will continue to communicate for future releases the transition from targeted to broad deployment status." Prior to this, Microsoft had released Build 1809 to targeted devices in order to determine that existing issues have been resolved and no new problems have appeared. This is why some Windows 10 users running on Windows 1803 have still not been offered the 1809 update as recently as 2 days ago. Now that Build 1809 is in broad deployment, it should be available to all users checking for updates in Windows Update. While the announcement states that Microsoft's Windows 10 release information page has been updated to indicate that build 1809 is classified as being in the "Semi-Annual Channel", as shown below it appears to have not been updated as of yet to reflect this change. Current listing of Windows 10 Servicing Options For users who have been unable to install build 1809 through Windows Update, you can check for new updates today or tomorrow and it should now be available. Source: Windows 10 Version 1809 Is Now in Broad Deployment, Available to Everyone (BleepingComputer)
  4. I created another LTSC for you guys and gals! Activates automatically. Special thanks to @s1ave77, Ratiborus, and all others who made this possible! 64 bit version: Site: http://www.mediafire.com Sharecode: /file/sbch643wuezp5ry/10.0.17763.194.RS_PRERELEASE_LTSC_MOD_OEMRET_X64FRE_EN-US.iso/file SIZE: 3.08 GB SHA1: 679814EFCE5E39D26551593A7D8D4684D251706F MD5: 6D39974466CDD5D6D296CB6DBAE236D1 CRC32: DD8A99E1 Original ISO Name: en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_4c97c86c.iso Removed: Defender, People, Fax, PPIProjection, IE, Connect Added: Edge, MS Store, DVD Player, patched files for 3rd-party themes, all updates, imagex, hash calculator, oscdimg, right-click desktop enhancements Wim Info: 32 bit version: Site: https://www.mediafire.com Sharecode: /file/g7ryu7swr0fwzvi/10.0.17763.194.RS_PRERELEASE_LTSC_MOD_OEMRET_X86FRE_EN-US.iso/file SIZE: 2.22 GB SHA1: 1A6D0531B5208D0172D0197F7A4ADC62112531B1 MD5: 859822AA43EF48771F1E0E5496A53C56 CRC32: EB5044C6 Wim Info: Images:
  5. On Tuesday, Microsoft released cumulative updates for Win10 versions 1803, 1709, 1703 and 1607 that address all of the acknowledged bugs (there were many) in those versions of Windoews 10. Usual Seeker of Queensbury rules apply: You only get them if you click Check for Updates. But where’s the fix for Win10 1809? Getty Images On the Third Tuesday of this month, Microsoft released cumulative updates for all of its surviving Windows 10 versions save one: KB 4487029 for Win10 version 1803 takes the build up to 17134.619; KB 4487021 for Win10 version 1709 moves the build to 16299.1004; KB 4487011 for Win10 version 1703 advances the build to 15063.1659; KB 4487006 for Win10 version 1607 and Server 2016 brings the build to 14393.2828 (yes, this version of Windows 10 has been rebuilt 2,828 times). Version 1809’s patch isn’t out yet – and I take that as great news. Microsoft’s taking its time rolling out 1809 “fixes.” That said, the latest cumulative update hasn’t appeared in the Windows Insider Release Preview Ring. So my fanboi squeal is a bit muted. Although there are lots of little bug fixes, the main ones nullify the acknowledged bugs in earlier releases of all the versions: Some users cannot pin a web link on the Start menu or the taskbar. The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Internet Explorer may fail to load images with a backslash (\) in their relative source path. Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. There’s no announcement about the additional legacy Access database bug. You have to wonder if Microsoft has finally found a solution to the Japanese date bug. It's certainly been trying long enough. Since December, Microsoft has been releasing these non-security cumulative updates on the third Tuesday of the month ("C" week). In November and earlier, they came out on the fourth Tuesday ("D" week). They’re colloquially known as “non-security,” but whether they contain some security components (or fixes for bugs in previous security patches) remains unclear. And you’ll only get them if you manually download and install them or if, in Windows Update, you click Check for Updates. That’s a deception I’ve railed against for months, but apparently somebody at Microsoft thinks that being a seeker – clicking Check for Updates – gives the updater permission to install these lurking patches, without notification or consent. We’re keeping track of problems on the AskWoody Lounge. Source: New non-security Win10 patches fix numerous bugs, but where’s version 1809? (Computerworld - Woody Leonhard)
  6. The biggest surprise in the February patching lineup is one that didn’t appear: the 'optional non-security' cumulative update for Win10 version 1809. Most – but not all -- bugs introduced by earlier patches are now fixed. Thinkstock/Microsoft Microsoft continues to hold Windows 10 version 1809 close to the chest. While all of the other Win10 versions have had their usual twice-a-month cumulative updates, the latest version of the last version of Windows, 1809, still sits in the Windows Insider Release Preview Ring. For most people, that’s excellent news. It seems that Microsoft is willing to hold off until they get the bugs fixed, at least in the 1809 releases. May I hear a “hallelujah” from the chorus? Mystery update bulldozer KB 4023057 hits the Catalog You’ve heard me talk about KB 4023057 many times, most recently in January. It’s a mysterious patch that Microsoft calls an “update reliability improvement” whose sole reason for existence, as best I can tell, is to blast away any blocks your machine may have to keep the next version of Windows (in this case, Win10 1809) from installing on your machine. KB 4023057 and its predecessor KB 4022868 have gone through 50 or so versions over the past three-plus years, and it’s always been distributed stealthily – you get it when you install updates, unless you go to great pains to block it. @PKCano has a thorough description of the tortuous procedure for preventing its installation. Now comes word from @abbodi86 that on Thursday, for the first time, KB 4023057 has appeared in the Microsoft Update Catalog. It’s not clear why the old bete noire has been elevated to Catalog status – and I doubt Microsoft will ever tell us. Old Access bugs fixed. Mostly. February’s earlier Windows patches wreaked havoc on old Access databases. In January, Access 97 file format databases got clobbered by all of the Windows updates. Then Access 95 databases got the shiv. It’s almost as if nobody tests the Win10 cumulative updates against older databases, wouldn’t you say? As of this writing, all is well (apparently), except for Win10 version 1809, which hasn’t yet received the Access 95 inoculation. Word to the wise: If you have an older database program that you really need to use, watch out. Fixing with a wing, a prayer, and a silver bullet There’s a smattering of new bugs introduced by the Patch Tuesday patches, and subsequently fixed by Third Tuesday patches. The most entertaining of the lot is the Internet Explorer backslash bug. Of course, you don’t use IE, but for those who do… February’s Patch Tuesday patches for Win7 and 8.1 contained this weird, acknowledged, bug: After installing this update, Internet Explorer may fail to load images with a backslash (\) in their relative source path. That bug, and several others, were fixed in the Third Tuesday Monthly Rollup preview patches – but those aren’t distributed through normal channels. You have to wait until later in March, when the Monthly Rollup Preview patches will (presumably) be added to the March Monthly Rollups. Got that? A bug in the February security update is fixed by a patch in the next month’s (presumably non-security) monthly rollup. Here’s where things get weird. On Feb. 19, Microsoft released KB 4491113, a “Cumulative update for Internet Explorer: February 19, 2019,” which is a silver bullet patch with one intent: This cumulative update includes improvements and fixes for Internet Explorer 11 that is running on Windows 8.1 or Windows 7, and resolves the following issue: Internet Explorer cannot load images that have a backslash (\) in their relative sources path. So we have a cumulative update, KB 4491113, that fixes a bug introduced in this month’s Monthly Rollups, but which is also fixed in this month’s Monthly Rollup previews. The previews fix other bugs as well, but I guess this one was problematic enough to warrant a single silver bullet. Except… now comes word (from an anonymous poster) that KB 491113 is causing problems: FWIW, this “silver bullet” isn’t quite ready to be fired; it caused problems with the game Halo: Spartan Strike by omitting some of the sound and then letting the game hang after a few minutes. It may also have caused some problems with videos on Firefox. Upon uninstalling, the Spartan is again killing Covenanters and Prometheans with full sound. If you’re using Win10, the bug was fixed in the Third Tuesday patches – except for Win10 1809, which doesn’t yet have a Third Tuesday patch. Moral of the story: Internet Explorer isn’t a browser. It’s a decorative appendage. To further complicate matters, the Win8.1 Monthly Rollup Preview, which fixes this bug, introduces a truly bizarre bug that enables Location Services and makes a nuisance of itself in the Notification (er, Action) Center. Windows 10 1809 still not ready for prime time Microsoft changed its terminology, again, but it hasn’t yet officially declared that version 1809 is ready for business deployment. You can think of that as CBB, or SAC-not-T, SP1, or VGBS (venerable gray beard status), but whatever hokey name you put to it, the fact remains that Microsoft has not yet come out and said that Win10 version 1809 is suitable for mass consumption. The official Windows 10 release information page still lists it as “Semi-Annual Channel (Targeted),” which is old terminology but with a judicious nod and wink – and with a dearth of additional reassurances – it’s clear that Microsoft isn’t yet recommending that businesses move onto the latest and greatest. Hard to say when that’ll happen, but there’s lots of pressure to brand Win10 1809 as “ready for business” (CBB, SAC, SP1, VGBS, whatever) before Win10 1903 arrives…. which should be in 3… 2… 1… Keep up on the parts of Windows that matter on the AskWoody Lounge. Source: Microsoft Patch Alert: After a serene February, Microsoft plops KB 4023057 into the Update Catalog (Computerworld - Woody Leonhard)
  7. Microsoft released -- the missing -- cumulative update KB4476976 for Windows 10 version 1809 and Server 2019 yesterday evening to the public. The company released cumulative updates for earlier versions of Windows 10 days ago but decided to test the update for Windows 10 version 1809 in the Release Preview ring before its official release. Microsoft changed its strategy in regards to cumulative update releases for the latest version of Windows 10 after the update fiasco of Windows 10 version 1809. Instead of releasing cumulative updates outright, like the company has done on older versions of Windows 10, it is pushing updates to the Release Preview ring first before releasing them. In other words, another round of testing and -- hopefully -- bug finding before the update is unleashed on the general population. KB4476976 for Windows 10 version 1809 and Server 2019 KB4476976 is available on Windows Update and as a direct download on the Microsoft Update Catalog website. Windows administrators who install the update manually need to make sure that the latest Servicing Stack Update is installed on the device. The update shares fixes with the recently released cumulative updates for earlier versions of Windows 10. In particular: Microsoft Edge may stop working with "certain display drivers". Third-party applications having difficulties authenticating hotspots. Promotion of non-root domains failed with error "The replication operation encountered a database error". More Japanese era calendar fixes. Compatibility issues with AMD R600 and R700 displays. Audio compatibility issues with games that use 3D Spatial Audio Mode through multichannel audio devices or Windows Sonic for headphones. FLAC playback issue (could stop responding) when using operations such as rewind. The policy "Prevent users from uninstalling applications from Start Menu" did not work. File Explorer stopped working when enabling Timeline and the "Allow upload of user activities" policy was set to disabled. Local Experience Packs could not be downloaded from the Microsoft Store if the language was set as the active display language. Some symbols appeared in "a square box on a text control". Two-way audio issues during phone calls for some Bluetooth headsets. TCP Fast Open was turned off on "some systems". Some applications lost IPv4 connectivity if IPv6 was unbound. Connectivity issue on guest virtual machines on Windows Server 2019. Creation of page file on a drive with the FILE_PORTABLE_DEVICE flag caused "Windows created a temporary warning" errors. Remote Desktop Services stopped accepting connections. An issue in Windows Server 2019 that causes a Hyper-V VM to remain at the bootloader screen for OS selection when restarting the machine. The rendering of end-user-defined characters in Edge. Ltotape.sys update to add support for Linear Tape-Open 8 (LTO-8) tape drives. The support page lists two known issues: Microsoft Edge may not load resources using local IP addresses anymore. Workarounds available (Add local IP address to list of Trusted sites). Microsoft Jet Database issue that throws the error "Unrecognized Database Format". Workarounds are available. Source: KB4476976 for Windows 10 version 1809 and Server 2019 released (gHacks - Martin Brinkmann)
  8. Here is the new debug beta version of BigMuscle's Aeroglass for Windows 10 1809. It is the updated DWMGlass.dll file. Just stop Aeroglass from Task Scheduler, Open Task Manager, and go to the details tab, and stop dwm.exe. You can then replace the DWMGlass.dll file in your Aeroglass folder with the new one, go back to Task Scheduler, and click on run. I put the debug command window into a virtual desktop so it is unseen. This does work on the new 19H1 builds, also. You can download the 1803 version here: http://www.glass8.eu/download Then download the beta here: Site: https://mega.nz Sharecode: /#!0EIXEAxY!siEDVHAj7tjQ-ObnLuKhH_bmTDq4ajJXbUAOz25XFwc
  9. Once again, Microsoft brings hope to avid Windows watchers as it uses the correct, defined method to test build 17763.167 of Win10 1809. Remains to be seen if this is a fly-by-night fix for a hastily pushed patch, or a sign that the new regime takes bugs seriously. Microsoft / IDG Two weeks ago we witnessed an amazing change in Microsoft’s approach to patching Windows 10. For the first time, Microsoft pushed a test version of a cumulative update to Win10 1809 out through the Windows Insider Release Preview Ring — which is exactly why we have a Release Preview Ring. Yesterday, lightning struck twice, with Microsoft releasing a new version of KB 4469342 to the Insider Release Preview Ring, bringing the latest test build of Win10 1809 to 17763.167. No, the new KB isn’t documented anywhere. We have no idea what it fixes. But that’s beside the point, really. The important fact is that Microsoft is now testing Win10 cumulative updates through its established Insider ring before releasing them to the outside world. Now, the key question is whether Microsoft will let build 17763.167 stew for a while before releasing it as an official update, or whether it will wait until it’s been through its paces. I can just imagine a Win10 ad with Orson Welles intoning, “We will push no swine before its time.” Does 11763.167 fix all of the acknowledged bugs in Win10 1809? Who knows? One of the listed Known Issues, which involves mapped drives failing to connect, still has this note: Microsoft is working on a resolution and estimates a solution will be available by the end of November 2018. It’s an old bug that affects other versions of Win10, but if Microsoft is going to fix it “by the end of November 2018,” the clock is ticking. There are also reports that attempting to use the Update Assistant to go from Win10 1803 to 1809 fails at 16% for those who have Developer Mode enabled — disable Developer Mode and all goes well. No idea if 17763.167 fixes that one, either. (Thx, Bogdan Popa at Softpedia.) Personally, I’d rather wait until next month’s Patch Tuesday, and get all of our Win10 1809 cumulative updates in one, well-seasoned dose. And I’d like to see that pattern repeated for as long as there are Win10 cumulative updates. As a service, ya know? It’s heartening to see Microsoft using the Windows Insider Release Preview Ring in the way it was originally intended. The primary problem with the Release Preview Ring is its name. As I explained more than two years ago: No doubt it was easier for Microsoft to roll the Release Preview function into the Windows Insider beta build machine, but that commingling has led to endless confusion. On the one hand you have beta builds — test copies of the next version of Windows. … On the other hand, you have Release Preview builds — precursors to the next cumulative update for the current version of Windows. The Windows Insider program caters to both those who are beta testing the next version of Windows and those who are testing the next cumulative updates to the current version of Windows. You bet it's confusing. … Microsoft has used the phrase "Release Preview" for all sorts of items over the years. It needs to give the "precursor to the next cumulative update" builds a different name. I’ve read many articles damning the original version of Win10 1809 as poorly tested and unworthy of release — singing to the choir, in this case. Many of those with an opinion say that Win10 1809 should’ve been released to the Insider Preview Ring prior to being released to the world at large. I’m sorry, but that’s not the case. Microsoft should’ve spent more time on the Insider Slow and Fast rings with 17763.55, the original build of Win10 1809. But 11763.55 shouldn’t have gone out to the Release Preview Ring. Ever. Microsoft needs to revamp the Ring terminology. It’s so confusing, even the ‘Softies in charge have bungled the releases. What we really need is a testing preview of the non-security parts of each cumulative update — for every supported version of Win10. Call it what you will, but right now we should have Release Previews for next month's cumulative updates to Win10 1809, 1803, and 1709, avoiding the hit-and-run release of second cumulative updates every month. Will Microsoft come to its senses? I have hope. Join us for the patch watch on the AskWoody Lounge. Source: New beta-test version of Win10 1809 arrives, and — mirabile dictu! — it’s in the Release Preview ring (Computerworld - Woody Leonhard)
  10. Somebody at Microsoft deserves a medal. There’s a new, test version of the next Win10 1809 cumulative update floating around – KB 4469342 – and it’s being distributed through the Insider Release Preview ring. That is precisely where it should be. Thinkstock I’m starting to think that the people now in charge of Win10 version 1809 know what they’re doing. First, we saw a rudimentary list of known bugs in 1809, along with a point-by-point notice of what’s being done, and what you can do to fix the bugs. At this moment, the list includes all of the major bugs that I’ve seen: Mapped drives don’t reconnect – there’s a script you can run every time you re-boot. MS “will provide updates in the 2019 timeframe.” Trend Micro’s OfficeScan and Worry-Free Business Security (love the irony) packages trigger bluescreens. MS is blocking rollout on machines with the bad Trend Micro software, and Trend Micro has issued updates. Older AMD Radeon HD2000 and HD4000 graphic processors trigger bluescreens. MS is blocking rollout on machines with those GPUs and “is investigating this issue.” That, my friends, is an amazing development. Now we’re seeing a revelation that’s nothing short of revolutionary. The folks in charge of Win10 1809 are using the Insider Release Preview Ring in precisely the way it was intended. This morning, Microsoft released KB 4469342, a new cumulative update for 1809 that brings the build number up to 17763.165. Instead of pushing it out the Windows Update chute – the default action for untested “C week” cumulative updates since the earliest days of Win10 – Microsoft put it in the Release Preview channel. Amazing. That’s just the way the Release Preview channel is supposed to work. As best I can tell, it’s never been done before. Here’s what Microsoft’s official Insider Program overview documentation says: Release Preview Ring If you want to be on the current public release of Windows 10 but still get early access to updates, applications, and drivers without taking the risk of moving to the Development Branch, the Release Preview Ring is your best option. The Release Preview Ring is only visible when your Windows build version is the same as the current Production Branch. The easiest way to go between the Development Branch to the current Production Branch is to reinstall Windows using the Media Creation Tool, see instructions at Download Windows 10, or, for Mobile, the Windows Device Recovery Tool, see instructions at Windows Phone Device Recovery. That’s the way to run a cumulative update railroad. The structure's been that way since the beginning. And finally, finally, somebody inside Microsoft decided to use the Insider Preview ring the way it was intended. Until this morning, we’ve seen “C week” or “D week” cumulative updates for Win10 versions that exclusively include non-security patches. They’re untested in the outside world before they're pushed out the Windows Update chute. Earlier this year, these untested non-security cumulative updates were released in the normal Windows Update cycle. Lately, they haven’t been pushed onto Win10 machines…unless you “Check for updates.” So there's been some improvement. The next big question: Will this cumulative update go out to all machines through Windows Update on Thanksgiving week (“C week” this month), or will Microsoft show some restraint – as it should – and hold the non-security update until next month’s Patch Tuesday? I have hope. Join the (suitably muted) celebration on AskWoody. Source: Kudos to Microsoft: Resurrecting the Release Preview ring for Win10 1809 brings 17763.165 to heel (Computerworld - Woody Leonhard)
  11. November Patch Tuesday largely looks like other Patch Tuesdays, but there are troubling reports of server problems, WSUS stumbles, new SSUs lurking in the manual-install background, and (even more!) bugs in the toxic Win10 version 1809. Thinkstock Yesterday Microsoft released security patches for 63 separately identified vulnerabilities and three new Security Advisories. Microsoft rates 12 of the security holes as “critical,” and 8 of those are for the Edge scripting engine. Only one has an actively known exploit, discovered by Kaspersky, on 32-bit Win7 and Server 2008 systems in the Middle East. Martin Brinkmann has his monthly summary on ghacks.net for an overview of the numbers and links. Dustin Childs picks up all the nuances in his Zero Day Initiative post. Short version: As usual, if you avoid Internet Explorer and Edge, you should be fine for now. But, again as usual, you’ll have to patch eventually. Two new Security Advisories contain some worthwhile updates: ADV180002, Guidance to mitigate speculative execution side-channel vulnerabilities, has been updated to include even more information about even more Spectre-like problems with Intel, AMD and ARM chips. ADV990001, Latest Servicing Stack Updates, finally (finally!) lists the latest SSU for every version of Windows. It’s a long, ugly list, but if you insist on installing updates manually (or if you got bit by error 0x8000FFF when installing a Win7 Monthly Rollup), you can now confirm if you have the latest version of the Windows Update updater. Remember, the updater isn’t smart enough to update itself, if you’re applying patches manually. The Servicing Stack Update spray @PKCano reports: There are new Servicing Stack Updates for Win10 that address the Bitlocker Device Encryption vulnerability CVE-2018-8566. If you install the November Cumulative Updates using other than Windows Update, you will need to install the Servicing Stack Update first. If you are using Windows Update, the SSU will be offered automatically. Win10 v1809 Build 17763.134 KB4465646 Win10 v1803 KB4465663 Win10 v1709 KB4465661 Win10 v1703 KB4465660 Win10 v1607 KB4465659 There’s a German-language report of a bug in the interaction between the latest Servicing Stack Update for Server 2016, KB 4465659 and this month’s Server 2016 cumulative update, KB 4467691. Poster Gaius Julius on the deskmodder.de forum reports (translated by deepl.com): One of the two updates tries to write into the UEFI of the server. This works for virtual machines as well. For physical machines of the brands DELL and HP this does not work, at least if CPUs of the series Xeon E5-26 ... of the versions v1 and v2 are still installed there. On Fujitsu machines it does not work with the above Xeon CPUs of versions E5-26 ... v3 and v4. The UEFI is totally shot up, hardware raids are torn apart etc. pp. Remotely you can't reach the boxes anymore, because the Intel management machine is also totally torn apart, if it wasn't switched off by the ADMIN for security reasons. No network adapter is detected anymore. No confirmation on that report, as yet. WSUS hiccups again There’s a report of a persistent failure by WSUS to download this month’s patches: We are seeing multiple independent WSUS servers failing to download content (patches) from Microsoft for this month’s batch. … WSUS servers have been established for years and no changes on them have been made recently nor have firewalls been touched. Content downloads started and were successful for a fraction of the patches, but then halted. This started afternoon hours EST. Eventlog error 364 is seen. 1809 under the microscope Of course, it’s much too early to install 1809, and Microsoft recommends that you wait until it gets pushed onto your machine rather than seeking it out, but if you’re feeling lucky (and don’t mind risking your machine for a paltry list of new features), installation from the Media Creation Tool will bring you to build 17763.107, and the first cumulative update (that is, the latest first cumulative update) will bring you to build 17763.134. EdTittel reports on Tenforums: I was able to transition from 17763.107 to 17763.134 by leaving the Insider Preview program (updates only flavor), restarting a couple of times, then updating to the KB that brings the PC up to 17763.134 level. All good now. All of my 1809 machines are now at 17763.134. What concerns me the most are the sporadic, but vocal, reports of problems with the just re-released Win10 version 1809, the September-October-November 2018 Update. We already know about the acknowledged bug with filename extensions not being assignable to specific programs, a bug first publicized last week by Chris Hoffman in HowToGeek. The same problem now appears as a known bug for Win10 version 1803, as well — going back all the way to the Sept. 26 re-release of the “Fourth Tuesday” patch for 1803. I’m also seeing reports of the Mapped Drive Connection to Network Share May Be Lost bug, but that one’s not unique to 1809. It’s been around a long time. @NetDef reports munged video with 1809 and AutoCad: I’m seeing some seriously nasty things with video (current drivers) and acceleration in the ’18 and ’19 versions in our test bed. Thinking we might be passing on this feature update entirely and stick with 1803 for the next year. Toolbar windows that leave ghosts behind when moved. Sudden dark screens in the drawings (but the application menu UI stays intact.) Odd flickering randomly. I haven’t yet heard any loud screams of pain stemming from this month’s Monthly Rollups and Cumulative Updates, but the day is still young. Thx to @PKCano, @NetDef Got a problem? Don’t we all. AskWoody Lounge. Source: Patch Tuesday problems include even more reported bugs with Win10 version 1809 (Computerworld - Woody Leonhard)
  12. Yesterday Microsoft explained in full detail all four conditions that led to catastrophic data loss when installing the first release of Win10 version 1809. Here’s what you can expect from the second wave of releases, builds 17763.17 and 17763.55. Thinkstock In one of the worst Windows rollouts in history — at least since Windows 3.1 — last week’s rollout of Win10 version 1809 left some PCs with empty Documents, Photos and other folders, and it managed to mangle user profiles for others. The net result was mayhem, with Microsoft yanking the 1809 upgrade three days later. Now, a week after the initial assault, we’re told that Microsoft has solved all the problems and has begun a test rollout of the new, improved, latest version of the last version of Windows. The new rollout is only going to the Windows Insider beta-testers who are enrolled in the Slow or Release Preview rings. (It can’t go out to the Insider Fast ring because that ring was pushed to 18252.1000, the first round of “version 19H1” betas, back on Oct. 3.) If you’re running Win10 version 1809 — bless your soul — or you’re contemplating moving to 1809, there are three builds that you need to be aware of: 17763.1 = the original release. Not available anymore. Upgrading to this build can zap all of the files in the indicated folders. 17763.17 = the version you get if you’re in the Slow or Release Preview rings. 17763.55 = the version you hit if you install Patch Tuesday’s Cumulative Update, KB 4464630. Here’s where we are, and how we got into this mess. Build 17763.1 — The Destroyer The problem with the original version of Win10 version 1809 lies in the installer. If you’re sitting on 17763.1 (type “About” in the search box), and you still have files in your Documents, Pictures, Music, Screenshots, Videos, Camera Roll and/or Desktop folders, you’re OK. (“OK” being a relative term. I continue to suggest that you roll back to your previous version of Win10 and wait for the major bugs to devour themselves. Version 1809 has very few improvements — none of which warrant sacrificing a real, working PC.) Microsoft claims it was a tiny problem: Last week we paused the rollout of the Windows 10 October 2018 Update (version 1809) for all users as we investigated isolated reports of users missing files after updating. … In this case the update was only available to those who manually clicked on “check for updates” in Windows settings. At just two days into the rollout when we paused, the number of customers taking the October 2018 Update was limited. While the reports of actual data loss are few (one one-hundredth of one percent of version 1809 installs), any data loss is serious. You can judge the veracity of that claim as you wish, but I’d note in passing that the rollout wasn’t officially halted until Friday night, more than three days after the Tuesday launch, and either a) one whole heckuvalot of people clicked on “Check for Updates,” or b) every single one of the scorched 0.01% complained loudly — most of them directly to me. What happened? Microsoft says there were three bugs in the way the installer treated files that were installed in pre-defined folders that had been redirected — moved from one location to another. This “Known Folder Redirect” feature can kick in silently, notably if you installed an early version of OneDrive. You can try to slog through Microsoft’s explanation, or read Peter Bright’s much more accessible take on Ars Technica. In any case, if you got hit, it wasn’t your fault. Except that “Check for updates” part. I wonder how many people clicked “Check for updates” expecting that Windows would, you know, check for updates, only to discover that the contents of their Documents and Photos folders had been obliterated. Windows as a service. Build 17763.17 — A partial reprieve Yesterday, Patch Tuesday, Microsoft started rolling out a new build for version 1809. If you’re in the Windows Insider program and your machine is set on the Slow or Release Preview ring, you saw an update yesterday, taking your machine from 17763.1 to 17763.17. See the flaw in that logic? In almost all cases this move doesn’t test the (badly) broken installer, the one that zapped files when moving from 1803 to 1809. Unless you’re on 1803 (or 1709), and switch to Windows Insider builds on the Slow ring, all you’ll be testing is the upgrade from a non-existent 17763.1 to a now-obsolete 17763.17. Let's hear it for rigorous beta testing. Build 17763.55 — Only the usual bugs Yesterday, Patch Tuesday, saw the release of KB 4464330, which brings any build of Win10 version 1809 up to build 17763.55. The most important change in 17763.55? It gets rid of the user profile deletion bug. Per the KB article: Addresses an issue where an incorrect timing calculation may prematurely delete user profiles on devices subject to the "Delete user profiles older than a specified number of day” group policy. In addition to all the security holes that got fixed on Patch Tuesday. Thus it would appear that if you get all the way to 17763.55, you’ll be beyond the two devastating bugs, and can feast on the usual, garden variety bugs. Of which there are many. What to do next If you lost all the files in your Documents, Photos, or other folders, don’t do anything. Shut down the machine and follow this official advice: To help our customers that may be impacted by this issue, Microsoft Support is assisting customers and trying to recover data for users who may have experienced related data loss. Microsoft retail stores support services also offer this same level of support in-store. While we cannot guarantee the outcome of any file recovery work, if you have manually checked for updates and believe you have an issue with missing files, please minimize your use of the affected device and contact us directly at +1-800-MICROSOFT or find a local number in your area. For more information, please refer to our Windows 10 update history page (KB article), which we are updating with new information as it is available. Based on the discussions posted online, it’s apparent that Microsoft doesn’t have a magic wand, and probably can’t do any better than a run of Recuva or similar undelete package. If you lost the contents of your Documents or Photos folder and can’t pull it back yourself, you’re probably SOL. Nonetheless, the monkey’s on Microsoft’s back to restore your data. Microsoft has committed to improving the Windows Insider Feedback Hub, to “provide an indication of impact and severity when filing User Initiated Feedback.” I expect that to work just about as well as a home anemometer in a Cat 3 hurricane. More on which later. Most of all, you need to remain vigilant. Microsoft’s going to release 1809 to the masses once again, sooner or later, and you’d be well advised to avoid it, until the debacle that Gregg Keizer describes as “lab rat” beta testing is over. Say, in five or six months. Get your questions answered, and join me in analyzing that 0.01% figure, on the AskWoody Lounge. Source: Win10 version 1809, take two: A guide to the builds and what they break (Computerworld - Woody Leonhard)
  13. Microsoft pulled the feature with the biggest “wow” factor from version 1809, but there are some hidden gems in this release. The big twice-a-year Windows 10 update is here ... except this time, it’s not so big. The Windows 10 October 2018 Update, a.k.a. version 1809, is perhaps the least impressive of the major updates since Windows 10 was introduced. It sports no big, new capabilities like Timeline, the flagship feature of the Windows 10 April 2018 Update. Still, it’s got some good sleeper features, a hidden gem or two, a few bombs, and a host of useful if not groundbreaking features. The release will be rolled out to Windows 10 users in phases, starting on October 9, so it might be some time before you see it arrive on your computer. If you want it sooner, you can try manually checking for updates. And if you want to delay the update, here's how to block it temporarily. Want to find out the good, the bad and the ugly of the Windows 10 October 2018 Update? Read on for details. *** Poster's note: This is a lengthy multi-page review, so use the link below for the complete article. *** Source: Review: Windows 10 October 2018 Update delivers modest but useful tweaks (Computerworld - Preston Gralla)
  14. Putting together hints from various reliable sources, it now appears as if the next version of Windows — build 17763 — has been signed off on. Ranjith Siji / IDG (CC0) Yes, it’s like reading chicken entrails, but all of the chicks seem to be peeping in unison. It now appears as if Win10 build 17763 — the one that’s currently available on the Windows Insider Fast and Slow rings — has been anointed the “RTM” version, in fact if not in name. WZorNet, the presumably Russian person/group that leaked many builds of Windows many years ago, posted his/her/its/their official announcement on Sept. 23: IDG Snazzy graphics, as usual. Frequent contributor Abbodi unearthed the latest version of WindowsUpdateBox — the program that’s been used to install the upgrade, going back to the ESD files in Win81, all the way up to the UUP files in Win10 1709 et seq. IDG The Details tab on the file properties dialog for the latest version of WindowsUpdateBox states, quite explicitly, that it is Product version 10.0.17763.1, modified Sept. 23. IDG Abbodi just put the final nail in the chicken entrails’ coffin. He found an ESD (= Electronic Software Download = upgrade) XML file that starts with <?xml version="1.0" encoding="UTF-8"?>= <PublishedMedia id="2072" release="20181002 RS5 RTM WU"> <Files> Which certainly points an accusing finger at the RTM version being distributed on Oct. 2. Of course, if this RTM is anything like the last five, we’ll have additional cumulative updates that roll out right around the time the final version becomes available for download. Thx, @abbodi86, @WZorNET, @gborn, @teroalhonen Join us for artificial popcorn on the AskWoody Lounge. Source: Win10 version 1809 'RTM,' build 17763, now expected to drop Oct. 2 (Computerworld - Woody Leonhard)
×
×
  • Create New...