Windows 10: Windows Update Not Working Build 1703

Hi, I was wondering if there's an issue with Windows Update or my PC. I've been trying to get this build right for a while, and just when I think I have it, I find another issue!

I'll give you a little background to start.

I built this PC to be a multi-purpose machine. I do video production/podcasting, video editing, normal office type activities, and home/personal use. I am trying to set it up where the OS is on the M.2 drive, software/programs are on my 840 EVO in RAPID Mode as my B: drive, and user data on a 250GB Toshiba HDD assigned to D:. At first, I partitioned the 960 so the OS was installed in 1 200GB partition and user data was in another 200GB partition, with roughly 65GB unallocated. Windows also created its 2 additional partitions. My PC was very slow and lagging, and was getting random BSOD's, so I wiped it and started fresh.

I reconfigured all my drives to have single partitions, with the exception of any MBR's created. I installed Win10 using the Media Creation Tool. I installed while connected to the Internet. Upon installation, I immediately updated Windows and restarted. Currently, I'm running Windows 10 Pro, Version 1703, Build 15063.0 Product ID 00330-80000-00000-AA558. Installed updates are:

• Security Update for MS Windows (KB4025342)
• Security Update for Adobe Flash Player
• Update for MS Windows (KB4022405)
• MS Visual C++ 2010 x86 Redistributable - 10.0.40129 (1) KB2565063
• MS Visual C++ 2010 x64 Redistributable - 10.0.40129 (1) KB2565063

After installing all updates and restarting, I copied and pasted everything from C:\Program Files and Program Files (x86) over to the 840 EVO assigned to B:.

I then went into the Windows Registry and made some minor modifications.

The first was changing the

string to 2147483650 to enable Num Lock on at startup.

Next, I went into

and modified the 6 program install locations (\Program Files, \Program Files (x86), \Program Files\Common Files, \Program Files (x86)\Common Files) to reflect the appropriate "B:" drive folders.

I then proceeded to

and made the same modifications in the appropriate keys/strings.

My next step was to copy all my user data (Music, Pictures, etc.) into the 250GB Toshiba HDD. I then opened Windows Explorer and navigated to This PC > C: > Users > [Username] > [Dir.], opened Properties > Location, and moved all data folders to the Toshiba drive assigned to D:.

Upon completion, I restarted the PC to make sure all the registry changes took effect. Everything seemed fine, so I performed a Windows Backup and saved a System Image, then proceeded to begin the tedious task of installing all my drivers and software...

When I finally finished installing everything the day before yesterday, I went to check over the entire system and confirm everything was up to date. When I went into Windows Update, I saw the message

with a "Check for updates" button below it. When I click the button, I get the sliding dots for several seconds, then the message immediately returns. No error codes. Nothing else crazy.

At this point, I've now scoured the Internet for 2 days and have tried just about every sensible repair I could find related to the topic. I've even run Tweaking.com's Windows Repair utility, which is basically an automated tool created to complete everything I had previously done manually! Nothing has worked.

I've read there have been numerous problems with Windows 10 and its updates, and have even had issues with previous updates/builds. Besides that minor hiccup, everything seems to be running stable, with the exception of not being able to install Flight Simulator X for some reason.

Here's a screen shot so you can see what I see in Windows Update:





Here are the 2 registry keys and 12 strings I changed:








And a view of my drive assignment/configuration:





If you need any other information (proof of a valid activation, log files, etc.), please just let me know and I'll get them up ASAP.

At this point, I've read others have had issues with the last KB4025342 update and am wondering if it's just a bug with this update. Any and all assistance would be much appreciated! I'm really NOT trying to wipe Windows and start all over yet again, but that seems to be the last available option if something's wrong... *Mad*Sick*cry*Confused*Banghead

:)

 

maskedbox.dll problem on windows 10 build 1703

Good Day,

we encounter on our problem before the windows update our program is working properly. but after we update it into build 1703 our program is not responding during file entry. it seems the maskedbox.dll is not working on new build of windows 10. any suggestion
or idea how to fix and allowed the maskedbox.dll to run on build 1703 windows 10

 

Windows 10 build

Simple question. Let's assume i install Windows 10 enterprise build 1703. Does automatic updates will update it automaticly to build 1709? Asking because currently have problems (shutdowns..) with build 1709 (most probably) and i am gonna to install from
scratch build 1703 and don't want windows to update it automaticly to 1709 again. Does build is lets say completly diffrent of other build? How it works.

 

My understanding is that this isn't supported and will give you problems, particularly with upgrade installations:

Further, note that even assuming you have modified all the references consistently, you are relying on programmers not using absolute paths hard coded to these locations. That is not an uncommon oversight.

 

Thanks for your reply, dalchina.

I understand. I know I didn't list all the troubleshooting steps I took. I should've mentioned that after I did the initial update after installation of Windows, I made a backup of the entire Current Version Registry key with the Windows default settings. Next, I made the modifications and saved that configuration as well. When I began having this issue, I immediately reverted to the original Registry configuration, but the problem remained the same. The only thing that changed was the default install location. Just doing some trial and error, I installed a program after restarting and it installed to the C: drive, which I then used Revo Uninstaller to remove.

Seeing the issue was still the same with Windows Update and the "stock" registry settings, I imported my modified registry file, restarted, and began further troubleshooting...

 

Hi, I doubt anyone can be sure that given the changes you've made you've actually got an entirely consistent installation (registry vs files and folders).

This is the Creator's build:

Now certainly a number of people reported slow boot, a few slow performance, the former usually having to be diagnosed to identify a driver issue.

I can't comment on the BSODs.

B: is an unusual drive letter - not normally used. I would research that, and avoid it at least initially (I can't recall the story offhand).

Personally, I would clean install with only my system disk connected, so as to ensure all Windows partitions ended up on that disk. (However, if the other disks have no Windows system partitions on them and no unallocated space you should be safe, of course).

 

Ahhhh. Guess I should've done a little homework first! After you mentioned an issue with drive assignment to B:, a quick Google search led me right back here to: Using B: or even A: as drive letters - Windows 10 Forums

I guess that explains it a bit... Looks like I'll be reserving A: and B: strictly for my optical drive (already on A*Smile, and a removable disk like my backups drive...

I guess since it looks like a fresh install is inevitable, I might play around for a few minutes first.. I wonder if I reassign the drive letters in Disk Management, then modify the registry settings and reboot, if it might begin to work, or if I'll just make everything I installed on to the current B: not work! Theoretically, I'm thinking I should mess everything all up! *Cool*Party*Start