![]() ![]() ICACLS C:\AppData /grant "CREATOR OWNER":F /T ICACLS C:\Windows /grant "NT SERVICE\TrustedInstaller":F /T ![]() I had a hunch about permissions being a mian culprit, from that Trojan.Muldrop, and sure enough - I think I may have been right. ![]() Please, read through before answering as many of the searches I've done on this issue - people seem to read the first line and drop in a common answer, and then it's silly. Sure the kid probably deserves a Fresh Install but he has a great many many many programs installed, Audio Engineering Software with multiple plug-ins from various sources and, I just don't want to wipe it and force him to go back through and install everything, especially when once I can get it up, it's going to be upgraded to Windows 10Īny assistance is greatly appreciated. The problem is I CANNOT FIND ANYWHERE ON THE WEB, how Windows files and Registry, on a basic level, should be structured - or I'd go through each individual file and identify if there are permission issues. Removed that, but that's what led me down the path of System file permissions being jacked up. Web and found a Trojan.Muldrop on a file from years ago though. I was able to get out of the boot loop but selecting Last Known Good Configuration, which again took me to black with Cursor, but at least when booting up Normally now, it doesn't boot Loop (thanks LKGC) Startup Repair is a bust, it simply just does not do a darn thing. I tried replacing the reg hive files in Windows\System32\Config with backup files from Regback, still nothing - in swapping those back (as I backed up the file first), it began boot looping 1sec after Windows logo appears on boot. It was at this time that I was able to boot and actually get a Windows 7 background, but still non-operable, just with cursor. There was one point where I CACLS all System32 folder an files to give Everyone, Full Access. I've tried CHKDSK, BCDBOOT, and BOOTREC all from a Windows 7 USB installer using WinPE It worked up until a couple weeks ago, the user couldn't give me much about what was going on when it went down but here are the facts: This custom build is pretty gnarly, but down to brass tacks. The guy that built it I replaced, as far as personal IT for my client. ![]() I'm working on a custom build, built a couple years back. Yes! It's true, No operation via Normal Boot, Safe Mode(any), or Low Res - can't imagine drivers being the issue. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |