Windows 10 Photo Bug? - Image Magnification Issues
Hello, Some Context of Problem Due to covid, my assessors have requested that I submit my evidence of coursework as attachments, within a limitation of submitting 15 files. Because some of this evidence has to be screen grabbed, the limitations of copy/pasting them inside a word document would limit the viewable resolution (text heavy therefore lots of small font), as well as word processors default with page breaks, margins etc. Therefore I saved my evidence as .jpgs for reasons explained below. I purchased screen manipulation software 'Snaggit', to stitch my evidence together to meet the maximum 15 pieces of evidence requirements, whilst also being able to annotate my work, another requirement set by my assessors. Issues With Viewing .jpgs Using Windows 10 Photos When my .jpg files were compiled and completed, I was able to zoom in with the Windows 10 Photos app, and scroll with a high fidelity of resolution, back at the end of June 2021 when I last properly revisited them. However due to waiting for the new academic year, my files could not be reviewed until now (October 2021). It seems Windows 10 Photos can't magnify up to 100% anymore, or view the files zoomed in to the degree I used to, which has prompted my assessors (who are likely using Windows 10 systems also) to be having the same issue (possibly?), but probably assume an caused at my end, and would not know this might be affecting other Windows 10 computers, if it is. May I ask if anyone else is having issues with magnifying .jpgs with Windows 10 Photos, that can't reach 100%, or is anyone aware of a bug with the Photo software? Troubleshooting Using Other Image Viewers I've saved the .jpgs to my Google drive, and can view them at close up without issues using the web image viewer, and have even downloaded software to bring back the previous Windows Photo Viewer (for Windows 7/8), which works fine also. Uninstalling / Reinstalling Photos App I have uninstalled and reinstalled the Photos app also, but to no avail. Perhaps if the app has been updated recently or the past few months, the update has caused this bug to occur (if it is not just me). Lastly This issue will really only be noticeable to others if they have a long or large file .jpg file, which is an unusual method of recording evidence. Thanks for your patience reading this.Three known bugs in the latest build of Win10 version 1903
Microsoft late Thursday declared Win10 version 1903 as ready for business deployment. The latest versions of Win10 1903 block installation of .NET 3.5. You may scoff that it’s an old version of .NET, but at least one large package — part of the ERP package known as SAP — requires .NET 3.5. Per Günter Born: [.NET 3.5] installation fails with the error: Microsoft-Windows-NetFx3-OnDemand-Package: 0x800f0954 The latest versions of Win10 1903 break some HP printers including. According to Tom Rogers on the Patchmanagement list: I installed the updated Sept 2019 Cumulative Update for Win10 x64 [1903] and it broke me printing to a network HP Color LaserJet Pro MFP M180NW… What happens in my case is the screen will flash, I hear the printer start, but then nothing. And then Windows closes any open windows. Almost like Windows Explorer restart. Job is not being held in the queue, printer is not offline (but HP software monitor says it is), this is a network printer I am testing on. The latest versions of Win10 1903 trigger black screens when running RDP. Per an anonymous poster: We have HP z2 g4 mini PCs – Windows 10 Pro 1903 – we have installed the updates above and we still get a black screen on remote desktop. We tried changing the systems we are remoting to to use the MS Basic Display Driver but that did not resolve the issue. Rebooting allows the system to work for an unknown amount of time before it stops working again until the next reboot. And confirmation, again anonymously: I installed KB4517211 (OS Build 18362.387) and still have the RDP black screen on HP EliteDesk 800 G5 SFF and HP 800 G3 Mini desktops. I ran HP SDM on both models to ensure all OEM drivers are current as of 9/27. rolling back the latest updates fixes the problem.Why bugs in Windows updates increased
Has the number of bugs in Windows updates increased in the past couple of years? If so, what is the reason for the increase in bugs? That's the question that former Microsoft Senior SDET Jerry Berg answered. Berg worked for 15 years at Microsoft and one of his roles was to design and develop tools and processes to automate testing for the Microsoft Windows operating system. He left the company after Windows 8.1 shipped to the public. Microsoft changed testing processes significantly in the past couple of years. Berg describes how testing was done in the late 2014 early 2015 period and how Microsoft's testing processes changed since then. Back in 2014/2015, Microsoft employed an entire team that was dedicated to testing the operating system, builds, updates, drivers, and other code. The team consisted of multiple groups that would run tests and discuss bugs and issues in daily meetings. Tests were conducted manually by the team and through automated testing, and if tests were passed, would give the okay to integrate the code into Windows. The teams ran the tests on "real" hardware in a lab through automated testing. The machines had different hardware components, e.g. processors, hard drives, video and sound cards, and other components to cover a wide range of system configurations, and this meant that bugs that affected only certain hardware components or configurations were detected in the process. Microsoft laid off almost the entire Windows Test team as it moved the focus from three different systems -- Windows, Windows Mobile and Xbox -- to a single system. The company moved most of the testing to virtual machines and this meant that tests were no longer conducted on real and diverse hardware configurations for the most part. Microsoft employees could self-host Windows which would mean that their machines would also be used for testing purposes. The main idea behind that was to get feedback from Microsoft employees when they encountered issues that they encountered during work days. Berg notes that self-hosting is not as widely used anymore as it was before. The main sources of testing data, apart from the automated test systems that are in place, comes from Telemetry and Windows Insiders. Windows Insider builds are installed on millions of devices and Microsoft collects Telemetry from all of these devices. If something crashes, Microsoft gets information about it. One of the issues associated with the collecting of Telemetry is that most bugs are not caught by it. If something does not work right, Microsoft may not be able to discern the relevant bits from Telemetry data. While it is in theory possible that users report issues, many don't and at other times, issues may go under because of other feedback that Microsoft gets from Insiders. Additionally, while Insiders may report bugs, it is often the case that necessary information is not supplied to Microsoft which poses huge issues for the engineers tasked with resolving these issues. Tip: you can view the Telemetry data that Microsoft collects. Back in 2014/2015, Microsoft's Testing team would be tasked with analyzing bugs and issues, and supplying engineers with the data they required to resolve these. Nowadays, it is Telemetry that the engineers look at to figure out how to fix these issues and fixes are then pushed to customer devices running Insider Builds again to see if the issue got fixed or if it created new bugs. One of the main reasons why Microsoft stopped pushing out new feature updates to everyone at once was that issues that were not detected by the processed could potentially affect a large number of customers. To avoid total disasters like the Windows 10 version 1809 launch, gradual rollouts were introduced that would prevent feature updates from being delivered via Windows Update to the majority of machines in the early days of the release. Closing Words Microsoft exchanged the in-house Testing team with Telemetry data that it gathers from Insider Builds that it pushes to consumer and business devices, and replaced much of the PCs that it used for testing with virtual environments. https://youtu.be/S9kn8_oztsA
Phone?
Sorry if this is in the wrong place, this is hardly an old codger friendly site! I'm guessing it's because of that enormous enormous update a few days ago (that prevented me from using the computer for a whole evening - thanks a bundle microsoft!) that my phone will no longer connect to the laptop. It doesn't appear in the files list. There's a message on the phone that I can't use bluetooth as well as something else I can't remember, which is new. I tried turning bluetooth off but it doesn't help. I've had to drag my ancient xp machine out of the attic just to move a couple of albums onto the phone. I have to say I've never known any of these pestilential updates to be improvements, dies anyone know how to cure the damage caused by this one? Many thanks
