Showing posts with label Windows 10. Show all posts
Showing posts with label Windows 10. Show all posts

Wednesday, March 4, 2020

Issues installing .NET Framework 3.5 on a Windows 10 Computer


On some Dell Computers I have worked on, when attempting to download .NET Framework 3.5 components, the install program will give out an error and refuse to download the install package.  

This cannot be fixed by using the Net Framework 3.5 Offline Package.  Other install options through the Programs and Features control panel also fail, as do running commands manually.

I believe the problem is caused by the installer being unable to see the Windows Install files located in the …Sources\sxs folder that are used to install OS components.  This issue usually does not affect computers that have had Windows 10 installed manually and does not affect ALL Dell install images.  But it has become enough of a problem that I have had to create documentation to fix it.

This fix requires you to use a Windows 10 installation on an external drive.

Step 1: Plug in Windows 10 external drive – make note of the drive letter it is assigned to.
Step 2: Open Command Prompt as Administrator
Step 3: Run the following command: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\x64\sources\sxs
Step 4: Source: refers to where on your Windows Install media you can locate …x64\Sources\sxs folder…


Step 5: DONE!

There are some other ways to do this, as well, but this seems to work the best.  One of the fixes I have run across involves downloading the ..Source\sxs.. folder from an unknown source.  That's a good way to get a virus!


I do not believe this is strictly a "DELL" issue.  I would look for this on computers where the manufacturer has a hidden partition containing the OS Recovery.  To date, I have not had this issue with computers where I have manually installed Windows 10.

Good luck!

Thursday, December 28, 2017

That's not a bug, that's a feature!

I have been having trouble with my Dell Latitude E5580 where desktop icons and documents will occasionally scale down to tiny sizes that are difficult to get back to proper size.

Normally, I dock my laptop and use an external keyboard for typing and a mouse for cursory things..  When I'm on the road, I just plop the computer down on a table.  Yay, mobile computing?

I knew my problems revolved around the Touch pad on the laptop and had experienced similar issues with previous laptops.  I addressed this by disabling the touch pad and using an external wired/wireless mouse and setting the touchpad to disable when the computer detected an attached external mouse.

Today, I didn't deploy my mouse, because I was busy with other projects and hadn't taken the time to retrieve my mouse.

Again, the scrolling and resizing issue reared its ugly head.  Enough!

The first issue is desktop icons have been resizing due to inadvertent touchpad strikes.  It is relatively easy to resize the icons by simply right-clicking on the desktop, selecting view, and then selecting the Icon size - small, medium or large.  But this is a nuisance that I would rather prevent.

Upon researching the issue, I found my my bear-sized thumbs were accidentally hitting the touchpad in such a way that it was creating a gesture used to resize.  I found this article on Microsoft's page.

https://answers.microsoft.com/en-us/windows/forum/windows_10-desktop-winpc/solution-inadvertent-resizing-of-text-and-icons/905c6d09-97b0-4aac-b85f-7f25b446c812?auth=1

By using this method, you can disable the gestures that are causing problems with item resizing.

In this case, this isn't a bug in software, but rather, unintentional use of a Windows feature.

Saturday, March 5, 2016

Moving on towards Windows 10 Pro

AS the natural successor to my Windows 8.1 Pro Article, I have decided to write this short article on my experiences on Windows 10 Pro.

First off, I like Windows 10 Pro.  There are quirks, bugs, and outright compatibility issues that are frustrating, but I feel 10 Pro is a very polished and refined successor to 8.1 Pro.  I have yet to run across significant issues that make a move to this OS a problem, and, in fact, I have moved the majority of my home machines from Windows 7 Pro to 10 Pro using the free upgrade from Microsoft.

When given the chance to upgrade in early August, I jumped at the offer, reserved my upgrades and began the process of moving my home machines from Windows 7 to Windows 10.  My personal desktop and laptop, I had upgraded to Windows 8.1 Pro during the fall of 2014.  I was very pleased with 9.1 and saw the changes in the Windows 10 Tech Preview released late spring of 2015 to be quite positive.

Second, the majority of users I have run across who have problems with Windows 10 also had the same complaints about 7, 8, and 8.1.  I don't feel they understood the consequences of upgrading, they didn't look at solutions to adapt, they simply saw something new and different and refused to change.  Or, in many cases, they didn't understand that their older software may not operate in a new OS environment.

I have run across some common complaints about how updating to Windows 10 ruined their computer or how much they hate the newer software they are being forced to use.

I work in IT and support Windows, Linux, and Mac systems in addition to Android and iOS platforms.  If you don't understand that every software update may change your working environment, then you need to stay away from those decisions.  At the same time, updates do provide solutions to existing bugs, security fixes, and may resolve conflicts that exist for others, but you may not be experiencing.  What I'm saying is when given the opportunity to read the documentation on an upgrade, do so.  This may give you the chance to prevent making your system change in a way you don't like.

Microsoft makes their living by selling software and hardware solutions.  That being said, you need to understand their motivation is to sell their new product, discontinue their old products, and move forward.  Hardware revisions come along that make old solution obsolete and a vendor can only support an obsolete system for so long.

This takes me to my third point.  Microsoft wants to get everyone they can onto the newest version of the OS.  This can be for many reasons - marketing failures with Windows 8, as of yet unknown security issues with Windows 7, or simply to wean people off older systems.  The Windows environment has changed significantly since Windows XP in 2002 - that was nearly 15 years ago now and if you want to stay current with the changes, you need to move to the newest version of OS.

You will find there are driver issues, software incompatibility, and some feature you will need to relearn.  If you're not ready or willing to do so, stick with Windows 7.

Lastly, support for Windows 7 is due to expire in 2019-2020 - this gives you plenty of time to retire older systems and move forward to the new OS.  Unless you have to have features to run the latest and greatest games and software, you really should consider postponing the upgrade until you decide to move to a newer computer.

In my case, I moved all of my machines that could handle the upgrades to Windows 10 Pro, after having tested it on my own computer.  I run multiple systems that share the same or similar hardware specs, so I understood which challenges I would face with the other systems.  I also had the option to go back to the previous OS and had taken precautions by backing up important files and programs I would need in case it didn't work out.