Answered by:
Why doesn't it work like the adverts? Win 7 to Win 10 upgrade

Question
-
Any suggestions for this?
After taking 1.5 hrs to upgrade Win 7 pro to Win 10 Pro on the first of our office workstations here is my sorry tale.
Office setup with several Win7 64 bit machines, bite the bullet to upgrade to Win 10 64bit.
Toes in the water, upgrade one machine to see if it burns...
Wow!
Looks great, boots up in seconds shuts down in seconds too, most (old) programs seem to work fine, no catch right?
WRONG!
In this office ONE machine has an Access DB on it, all other machines are linked via a front end to the back-end of the DB stored on that machine.
There are only a few users and this works fine, until... The Win 10 user now cannot see the shared folder that the DB is on and the front end of the Access DB will not connect. This was FINE before the Win 10 upgrade.
(update, The Win 7 users do not see the Win 10 on the network, the Win 10 user does not see the Win 7 users any more)
All users have full read / Write permissions so nothing should have changed.
I get an error code in trying to view the Folder - 80004005 = I don't work, nothing more specific than that.
PLEEEESE can someone help with this it is holding us up work-wise and upgrade wise, I cannot upgrade the rest of the machines in the office if none of them can see the DB.
Yes I know there is a possibility that if I upgrade the machine with the Access DB on it then all 'might' be fine but I'd rather get to the bottom of this.
Here's what I tried.
Add the user again, set/reset share permissions
On the 'locked' machine add the drive share again
Several reboots.
Firewall checks, on and off
Firewall rules added
All to no avail.
Opening Access from that machine just gives "Not a valid path." Well let me tell you you stupid machine...
Having extensively Binged and Googled, nothing I find fits the bill.
I did see one post that said access denied etc, but this fix involved fiddling with REGEDIT to my mind that should not be done this side of h*ll. The upgrade should do just that - upgrade. not degrade.
http://www.dedoimedo.com/computers/windows-10-network-share-access.html
"Network shares, like other Windows machines you may have in your environment, are no longer accessible. Best of all, they worked fine right up until the upgrade."
Sorry for the rant but I have been tied up for days on a 1 hour (upgrade) job.
Can anyone suggest anything, or has anyone encountered similar issues, this is halting progress, I've half a mind to restore to Win 7 but that is a retrograde step as there must be an answer somewhere.
Thanks in advance. McP.
Thursday, September 1, 2016 8:26 AM
Answers
-
I don't know how to use this tool yet
Don't overlook the Count Occurrences tool. When there are no good ideas about what to look for I usually suggest filtering with Operation Is Write and then using Count Occurrences on the Path field, to get a list of potential diagnostics. However, in your case I imagine it would be useful to try it with the Result field without filtering. ; )
Good luck
Robert Aldwinckle
---- Proposed as answer by MeipoXuMicrosoft contingent staff Wednesday, September 14, 2016 7:26 AM
- Marked as answer by Kate LiMicrosoft employee Sunday, September 18, 2016 5:08 AM
Friday, September 9, 2016 4:39 PM -
(update, The Win 7 users do not see the Win 10 on the network, the Win 10 user does not see the Win 7 users any more)
Which version of 10 are you on? Is NetBIOS enabled?
When it prompts for a user put ComputerName\Username that being the computer name of the target Windows 7 machine with DB you are trying to connect to.
I tried that it still says push off.
File sharing was the first thing I turned on, it still says push off.
Try first manually entering the credentials in Credential Manager (Control Panel > Credential Manager > Windows Credentials > Add a Windows credential)
- Edited by john.b_ Saturday, September 10, 2016 12:38 AM
- Proposed as answer by MeipoXuMicrosoft contingent staff Wednesday, September 14, 2016 7:26 AM
- Marked as answer by Kate LiMicrosoft employee Sunday, September 18, 2016 5:08 AM
Saturday, September 10, 2016 12:31 AM
All replies
-
Clear any saved credentials on the Windows 10 machine for the DB machine, then try to connect. When it prompts for a user put ComputerName\Username that being the computer name of the target Windows 7 machine with DB you are trying to connect to.
Have you enabled Turn on network discovery on the Windows 10 machine under the current network profile. Right click the network icon near the clock, choose Open Network and Sharing Centre, select Change advanced sharing settings.
Thursday, September 1, 2016 7:12 PM -
Hi RobMcP2,
The main issue is that it is not available to access the shared folder(DB) after upgrading to Windows 10, right?
Since the issue occurred after the upgrade, we should ensure the DB is compatible with Windows 10. Please confirm this with the DB support.
Please try the following command line to force the Windows 10 machine to use SMB1.0 to access the shared folder.
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
Re-enable:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto
If there still be an "Access denied" error, please refer to the following link to troubleshoot with process monitor tool.
Using Process Monitor to solve any problem, including DebugDiag
https://blogs.msdn.microsoft.com/benjaminperkins/2013/05/03/using-process-monitor-to-solve-any-problem-including-debugdiag/Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- Edited by MeipoXuMicrosoft contingent staff Friday, September 2, 2016 7:29 AM
Friday, September 2, 2016 7:28 AM -
Thanks both for the replies, sorry for the delay in responding. This should have been a quick job, as usual it has not been so.
Mr Happy response.
When it prompts for a user put ComputerName\Username that being the computer name of the target Windows 7 machine with DB you are trying to connect to.
I tried that it still says push off.
File sharing was the first thing I turned on, it still says push off.
The database BETTER be compatible, both machines were all originally Win 7 64 bit running office 2013, so the DB is Access 2103.
Since the upgrade the Win 10 machine cannot access (other than intermittently) the database.
I tried the command prompts you suggested, they all executed correctly, we tried accessing the files, no luck, though the user can see the Database PC on their network view, just not access it.
Then we tried a restart to see if that was needed. that did not help either.
I will look at your other suggestion on the Procmon option.
I can't say I am too happy about this, I run a small business, and whilst I really appreciate help that people on this forum supply, I don't appreciate the fact that this should be a simple process (which it started as) it should also NOT BE FLAKY.
Sometimes the user can access the DB, first it would not let them see it, then it did, now it doesn't.
There is no consistency which makes tracking it harder. I really have more important things to do.
As a result I am reconsidering installing Win 10 on the other machines because the last thing I need is a room full of users whinging (Like me!)
I know that I could (possibly) fix the problem by Win 10-ing all the machines, but judging from the state of thing at the moment I might make things worse.
If the Procmon helps I will update again.
Thanks all. McP
Tuesday, September 6, 2016 9:37 AM -
UPDATE,
I tried running Procmon on the machine with the DB (Win 7) on it to see how the tool worked)
The instructions on your link were followed to the letter, I still don't see any listed information in the large window.But I played around a bit and got a little more to see
I don't know how to use this tool yet but I am playing around with it, it looks pretty good, but has not pinned anything down yet, so still looking.
Little bit stuck here.
McP.
- Edited by RobMcP2 Tuesday, September 6, 2016 10:25 AM
Tuesday, September 6, 2016 10:01 AM -
Hi,
How about the issue, is there anything to update?
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.comFriday, September 9, 2016 8:08 AM -
I don't know how to use this tool yet
Don't overlook the Count Occurrences tool. When there are no good ideas about what to look for I usually suggest filtering with Operation Is Write and then using Count Occurrences on the Path field, to get a list of potential diagnostics. However, in your case I imagine it would be useful to try it with the Result field without filtering. ; )
Good luck
Robert Aldwinckle
---- Proposed as answer by MeipoXuMicrosoft contingent staff Wednesday, September 14, 2016 7:26 AM
- Marked as answer by Kate LiMicrosoft employee Sunday, September 18, 2016 5:08 AM
Friday, September 9, 2016 4:39 PM -
(update, The Win 7 users do not see the Win 10 on the network, the Win 10 user does not see the Win 7 users any more)
Which version of 10 are you on? Is NetBIOS enabled?
When it prompts for a user put ComputerName\Username that being the computer name of the target Windows 7 machine with DB you are trying to connect to.
I tried that it still says push off.
File sharing was the first thing I turned on, it still says push off.
Try first manually entering the credentials in Credential Manager (Control Panel > Credential Manager > Windows Credentials > Add a Windows credential)
- Edited by john.b_ Saturday, September 10, 2016 12:38 AM
- Proposed as answer by MeipoXuMicrosoft contingent staff Wednesday, September 14, 2016 7:26 AM
- Marked as answer by Kate LiMicrosoft employee Sunday, September 18, 2016 5:08 AM
Saturday, September 10, 2016 12:31 AM -
Hi,
How about the issue, is there anything to update?
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.comFriday, September 16, 2016 9:42 AM