F5F Stay Refreshed Software Operating Systems Windows 10 Pro and Ownership Rights

Windows 10 Pro and Ownership Rights

Windows 10 Pro and Ownership Rights

Pages (2): 1 2 Next
A
AdamDrong
Junior Member
31
10-22-2017, 12:10 AM
#1
Hello everyone, I just reinstalled Windows 10 Pro and have been facing some unusual crash issues. I downloaded a Windows debug tool to examine memory dumps, but I keep seeing messages like "You do not have permission to open this file." Even though I’m the admin and took ownership, access is still denied. My system has specs like a 7700K Aorous Z270 Gaming with 5GB RAM, Samsung Pro 960 NVMe drive, and a 1080TI FE on water. What’s happening with the installation? Should I try reinstalling now?
A
AdamDrong
10-22-2017, 12:10 AM #1

Hello everyone, I just reinstalled Windows 10 Pro and have been facing some unusual crash issues. I downloaded a Windows debug tool to examine memory dumps, but I keep seeing messages like "You do not have permission to open this file." Even though I’m the admin and took ownership, access is still denied. My system has specs like a 7700K Aorous Z270 Gaming with 5GB RAM, Samsung Pro 960 NVMe drive, and a 1080TI FE on water. What’s happening with the installation? Should I try reinstalling now?

I
imTri
Posting Freak
786
10-30-2017, 05:20 PM
#2
Some essential system files remain unavailable by default, even for admin access, which is typical.
I
imTri
10-30-2017, 05:20 PM #2

Some essential system files remain unavailable by default, even for admin access, which is typical.

C
chrisvzla1
Member
68
10-31-2017, 09:01 PM
#3
Microsoft has significantly altered file access settings in Windows 10. Their approach assumes restricting the PC owner prevents undesirable actions. Naturally, preventing someone from accessing their own machine contradicts the intended purpose of PC ownership. The company often struggles to grasp the broader context, exhibiting traits reminiscent of a psychopath. To resolve permission issues, follow these steps: Turn off Admin Approval – press Windows + R, type 'secpol.msc' and hit Enter. Confirm in the window that appears. Navigate to Local Security Policy, click Security Options, scroll down and disable User Account Control. Save changes by clicking Apply and OK, then restart the device.
C
chrisvzla1
10-31-2017, 09:01 PM #3

Microsoft has significantly altered file access settings in Windows 10. Their approach assumes restricting the PC owner prevents undesirable actions. Naturally, preventing someone from accessing their own machine contradicts the intended purpose of PC ownership. The company often struggles to grasp the broader context, exhibiting traits reminiscent of a psychopath. To resolve permission issues, follow these steps: Turn off Admin Approval – press Windows + R, type 'secpol.msc' and hit Enter. Confirm in the window that appears. Navigate to Local Security Policy, click Security Options, scroll down and disable User Account Control. Save changes by clicking Apply and OK, then restart the device.

A
Aunorine
Member
130
10-31-2017, 09:19 PM
#4
Thanks for the input @Delicieuxz. I verified my configurations and everything appears to be permitted or active. It's unusual that recently I could access the memory.dmp file from WinDgb without trouble, but now it's refusing access. There have been two BSODs in the past four hours, each distinct. The diagnostic codes were 0x0000003b and 0x00000139. If I had the minidump, I might identify the issue or submit it for assistance. I also encountered a first stop code earlier this week and believed it was fixed after reverting my NVIDIA drivers, which seemed to bring stability until last night when the crash resumed during gameplay. I also ran a chldsk, which restored me to recovery mode and performed a system repair—took roughly 5 to 10 minutes before restarting Windows. I'll monitor the outcome. Additionally, I used Samsung Magician to inspect my NVMe drive and two 850 EVO drives; everything checked out.
A
Aunorine
10-31-2017, 09:19 PM #4

Thanks for the input @Delicieuxz. I verified my configurations and everything appears to be permitted or active. It's unusual that recently I could access the memory.dmp file from WinDgb without trouble, but now it's refusing access. There have been two BSODs in the past four hours, each distinct. The diagnostic codes were 0x0000003b and 0x00000139. If I had the minidump, I might identify the issue or submit it for assistance. I also encountered a first stop code earlier this week and believed it was fixed after reverting my NVIDIA drivers, which seemed to bring stability until last night when the crash resumed during gameplay. I also ran a chldsk, which restored me to recovery mode and performed a system repair—took roughly 5 to 10 minutes before restarting Windows. I'll monitor the outcome. Additionally, I used Samsung Magician to inspect my NVMe drive and two 850 EVO drives; everything checked out.

D
DapperMD
Member
153
11-01-2017, 01:58 AM
#5
These error codes point to corrupt drivers, as indicated by available searches. The specific code 3b often relates to a graphics driver (display adapter or video), with other causes including antivirus software, memory issues, or mapping problems. BCCode 3b 0x0000003b usually signals excessive paged pool usage, possibly from user-mode graphics drivers interfering with kernel code. Possible fixes include removing manually installed drivers and trying again. Removing a faulty graphics driver, such as the Nvidia driver via Display Driver Uninstaller, can sometimes resolve the issue.
D
DapperMD
11-01-2017, 01:58 AM #5

These error codes point to corrupt drivers, as indicated by available searches. The specific code 3b often relates to a graphics driver (display adapter or video), with other causes including antivirus software, memory issues, or mapping problems. BCCode 3b 0x0000003b usually signals excessive paged pool usage, possibly from user-mode graphics drivers interfering with kernel code. Possible fixes include removing manually installed drivers and trying again. Removing a faulty graphics driver, such as the Nvidia driver via Display Driver Uninstaller, can sometimes resolve the issue.

L
LunaCraftXY
Junior Member
2
11-01-2017, 09:21 AM
#6
Hey there, Delicieuxz. I've already handled those steps. My initial idea and check on the dump file were about display drivers. I made sure no Intel drivers were installed, then I updated the NVIDIA drivers and rolled back. The ongoing crashes and the inability to read the dump files are confusing me. After a recent reinstall a few weeks ago, I didn’t notice any problems accessing anything in C:Windows, but now it feels like I’m completely blocked. It’s puzzling. The only reason I did a reinstall was because I dismantled my X99 system and temporarily moved my 7700K for the time being, until I rebuilt everything and added the NVMe drive.
L
LunaCraftXY
11-01-2017, 09:21 AM #6

Hey there, Delicieuxz. I've already handled those steps. My initial idea and check on the dump file were about display drivers. I made sure no Intel drivers were installed, then I updated the NVIDIA drivers and rolled back. The ongoing crashes and the inability to read the dump files are confusing me. After a recent reinstall a few weeks ago, I didn’t notice any problems accessing anything in C:Windows, but now it feels like I’m completely blocked. It’s puzzling. The only reason I did a reinstall was because I dismantled my X99 system and temporarily moved my 7700K for the time being, until I rebuilt everything and added the NVMe drive.

S
SA_minecraft
Member
203
11-01-2017, 11:00 AM
#7
Additionally, I'm encountering a BSD stop code 0x0000001e. Based on my understanding, this seems connected to a RAM problem. Any insights?
S
SA_minecraft
11-01-2017, 11:00 AM #7

Additionally, I'm encountering a BSD stop code 0x0000001e. Based on my understanding, this seems connected to a RAM problem. Any insights?

T
theonlyraider
Member
166
11-03-2017, 12:29 AM
#8
I believe we should eliminate all administrator rights filtering so Windows 10 functions like a standard OS, simply following instructions from the system and license owner. However, I think there shouldn't be any need for Windows 10 to always run as administrator when using applications, especially if you're logged in as the admin account. Even for users with admin privileges, there are still situations where Windows blocks actions like downloading, creating, or copying files to secondary drive roots. The settings I discussed remove these confusing and arbitrary cases where permission issues arise.
T
theonlyraider
11-03-2017, 12:29 AM #8

I believe we should eliminate all administrator rights filtering so Windows 10 functions like a standard OS, simply following instructions from the system and license owner. However, I think there shouldn't be any need for Windows 10 to always run as administrator when using applications, especially if you're logged in as the admin account. Even for users with admin privileges, there are still situations where Windows blocks actions like downloading, creating, or copying files to secondary drive roots. The settings I discussed remove these confusing and arbitrary cases where permission issues arise.

J
jambalaia93
Member
224
11-13-2017, 04:32 AM
#9
I think I'll be reinstalling Windows since things aren't working right. I can't retain ownership, and every time something crashes, my settings reset in games and AutoCAD, etc. It's frustrating now.
J
jambalaia93
11-13-2017, 04:32 AM #9

I think I'll be reinstalling Windows since things aren't working right. I can't retain ownership, and every time something crashes, my settings reset in games and AutoCAD, etc. It's frustrating now.

T
trayman03
Member
51
11-13-2017, 05:19 AM
#10
You may need to reinstall. Have you already attempted resetting all access rights in the Advanced Security Settings? If not, proceed with this instructions. Instead of right-clicking on "Example Folder" and adjusting its permissions, click the root C:\ and continue with the same actions.
T
trayman03
11-13-2017, 05:19 AM #10

You may need to reinstall. Have you already attempted resetting all access rights in the Advanced Security Settings? If not, proceed with this instructions. Instead of right-clicking on "Example Folder" and adjusting its permissions, click the root C:\ and continue with the same actions.

Pages (2): 1 2 Next