psydii Posted October 10, 2018 Posted October 10, 2018 That profile bug exists in earlier releases, it needs to be back ported.
free780 Posted October 10, 2018 Posted October 10, 2018 I'm sure more CUs will appear in coming weeks. I'd keep testing for the next few months before deploying. It's a shame 1709 had very few issues but 1803 and 1809 seem to hit major bugs.
Jaan Posted October 10, 2018 Posted October 10, 2018 Has anybody found the ADMX template downloads with the excel sheet with the new gpo added? I'm aware i can get the admx from a client machine. cheers
Arthur Posted October 10, 2018 Author Posted October 10, 2018 Has anybody found the ADMX template downloads with the excel sheet with the new gpo added? Nothing yet. https://twitter.com/WindowsUK/status/1048615840185290753
SBDDrumB Posted October 10, 2018 Posted October 10, 2018 Why do Windos keep doing this to us - the job is hard enough
psydii Posted October 10, 2018 Posted October 10, 2018 Psydii's rule for Feature update deployment: If ADT or ADMX updates aren't out yet, then the build is not enterprise ready. Generally we don't fully commit to a new Feature Update release until the ISO has been updated after the third CU. We have it rolling out quiet widely as an update via SCCM Software Centre after the second CU, we also take a first pass at our main OS deployment image. After the updated ISO is release we pivot our image to the new version, and release the Feature Update to all client, unless of course show stopping issues remain. Meanwhile we of course release the CU's etc promptly for all deployed versions of Windows using ADRs - often they contain enhancements that make the future Feature Update go more smoothly. (see Intel graphics drives this time around).
Zoom7000 Posted October 10, 2018 Posted October 10, 2018 Still no sign of 1809 on VLSC since it was pulled. I managed to download LTSC 2019 before it was pulled and create an image. Gonna try install the cumulative update now and see how that goes.
mullet_man Posted October 10, 2018 Posted October 10, 2018 I've learned not to jump in with any new release of Windows 10, remember having issues with 1607 iirc and WSUS. Best thing is to wait a month before deploying out to anyone other than a few test machines. Normally install on my work PC to test my In place upgrade on SCCM but didn't even manage to the ISO off VLSC before it was pulled all think I'll wait for the updated ISO to come out.
free780 Posted October 11, 2018 Posted October 11, 2018 Just keep testing when the ISO/Admx etc are released. I'm starting to think having a PC on insider might be a good idea.
Arthur Posted October 11, 2018 Author Posted October 11, 2018 More Windows 10 October update woes? HP users report BSOD after Tuesday patch ^ This sounds like it's more HP's fault than Microsoft's?
sigma Posted October 11, 2018 Posted October 11, 2018 More Windows 10 October update woes? HP users report BSOD after Tuesday patch ^ This sounds like it's more HP's fault than Microsoft's? More detail here from "Woody" https://www.computerworld.com/article/3313317/microsoft-windows/theres-a-rash-of-wdfviolation-blue-screens-on-win10-hp-computers-with-an-as-yet-unknown-cause.html I'd say the jury is still out on whose fault it is.
johnpd Posted October 11, 2018 Posted October 11, 2018 has anyone found an updated gpo spreadsheet so we can see what has been added (bar disabling printing in edge which is probably a good thing as it kills print queues) Has it been disabled now? How do I get my hands on this beauty?
Arthur Posted October 12, 2018 Author Posted October 12, 2018 How do I get my hands on this beauty? https://docs.microsoft.com/en-us/microsoft-edge/deploy/change-history-for-microsoft-edge?tabs=2018 1
Arthur Posted October 12, 2018 Author Posted October 12, 2018 I'd say the jury is still out on whose fault it is. Definitely HP's fault! 😞 https://support.microsoft.com/en-us/help/4468372/hp-devices-may-experience-blue-screen-error-wdf-violation-after-instal Summary In working with HP, Microsoft has identified an HP driver with known incompatibility with certain HP devices on Windows 10 versions 1803 and 1809. On 11 October, Microsoft removed the driver from Windows Update to reduce the number of devices affected. Additionally, we have released KB4468304 to remove the incompatible driver from devices pending reboot. HP is actively working on this issue. Symptoms After installing the HP keyboard driver (version 11.0.3.1), via Windows Update or manually, HP devices may experience a blue screen error: WDF_VIOLATION. Cause This driver has a known incompatibility with certain HP devices on Windows 10 versions 1803 and 1809. HP aren't exactly known for writing good drivers.
Arthur Posted October 13, 2018 Author Posted October 13, 2018 Windows 10 Audio Not Working After Installing Latest Windows Updates Lot's of reports are coming in that Windows 10 users are finding that their audio is no longer working on their computer after installing the latest Windows updates. Windows Updates have become a complete mess lately, with the latest October 2018 Update deleting user's files, Patch Tuesday updates causing crashes because of incompatible keyboard drivers, and now users are finding that their audio drivers are broken. While there has been no word about this from Microsoft, numerous users are posting on Reddit, the Microsoft forums, and Twitter about their audio no longer working after installing this week's Patch Tuesday updates. Windows 10 just states "No Audio Device is installed". Fix/Workaround... www.reddit.com/r/Windows10/comments/9nc4jd/no_audio_after_recent_update/e7ln0n3 Go into your Device manager Go to System Devices Locate an audio driver that has SST in it Right click, select Update Driver, Choose browse from computer Select High Definition Audio Click Next, SST will disappear and you should have Audio back
mavhc Posted October 13, 2018 Posted October 13, 2018 HP audio does seem rather rubbish, the Probook 440 G4 laptops we bought have a broken audio driver causing the annoying cortana voice on setup to be distorted, really bad impression, WU gets a fixed driver
sigma Posted October 13, 2018 Posted October 13, 2018 Definitely HP's fault! 😞 https://support.microsoft.com/en-us/help/4468372/hp-devices-may-experience-blue-screen-error-wdf-violation-after-instal HP aren't exactly known for writing good drivers. Looks like it. HP's recent changes to their drivers download pages aren't great either and not to mention when they just don't download.
Arthur Posted October 14, 2018 Author Posted October 14, 2018 The audio issue has now been fixed. https://blogs.msdn.microsoft.com/matthew_van_eerde/2018/10/12/if-windows-update-sent-you-intel-audio-controller-version-9-21-0-3755-by-mistake-uninstall-it An Intel audio driver was incorrectly pushed to devices via Windows Update for a short period of time earlier this week. After receiving reports from users that their audio no longer works, we immediately removed it and started investigating. If your audio broke recently, and you're running Windows 10 version 1803 or above, please check to see if the incorrect driver was installed. To regain audio, we recommend you uninstall the driver. UPDATE 2018-10-13: Windows Update KB4468550 now removes the driver automatically from systems that received it incorrectly.
Duke5A Posted October 15, 2018 Posted October 15, 2018 OK, they fixed the data loss issue, but has it been posted back up to VLSC for download yet? It's missing from mine.
CHiLL Posted October 15, 2018 Posted October 15, 2018 OK, they fixed the data loss issue, but has it been posted back up to VLSC for download yet? It's missing from mine. Not yet, or at least it's not on mine either. Neither is Server 2019.
Arthur Posted October 15, 2018 Author Posted October 15, 2018 has it been posted back up to VLSC for download yet? It's missing from mine. It's probably not going to appear on VLSC for a week or two.
Duke5A Posted October 15, 2018 Posted October 15, 2018 So I'm not blind this time. I can't tell you how many times my wife asks for something in the fridge and I can't find it, only for her to step over and pull it off of the shelf that was right in front of my nose.
free780 Posted October 15, 2018 Posted October 15, 2018 Microsoft has moved from "Move fast and break things" to "Move slow and test things".
DJ-1701 Posted October 16, 2018 Posted October 16, 2018 Special Instructions We have paused the rollout of the latest feature update to Windows 10 and Windows Server, inclusive of versions 1809 and 2019, for all users as we investigate isolated reports of users missing some files after updating. We have removed all associated media from download sites and plan to refresh it with a new release. If you have already downloaded media, please don’t install it and wait until more information is available to proceed. We apologize for any inconvenience this may have caused. We will provide an update when refreshed media is available. For reference, we also have a KB article with additional information here. Known issues are documented here. I wonder how long before they actually release the ISO though as apparently the update was fixed last week...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now